On 17/10/24 12:16 +0300, Сергей wrote:
Hello All,
I found a bug in gcc-13.2.0-llvm-17.0.5-mingw-w64ucrt-11.0.1-r3 for Windows.
This bug occurs when translating the file "bug.c" with the -O3 option. There is
no error when translating it with the -O2 option.
To check this bug, download bug.c f
On 26/09/24 04:44 +, Jason Mancini wrote:
Problem happens in 14.2.0, 13.2.0, 12.2.0
Doesn't seem to happen in 10.2.0 or 11.2.0
Only seems to happen for -std=c++17/14/11, but not for c++20/23/26.
Only seems to happen for -O2, but not -O0 / -O1 / -O3.
Happens for vector, but not deque or list.
Hi,
It's not useful to CC the gcc-bugs list with patches. Please just send
the patch to the gcc-patches list (and any other appropriate lists,
like libstdc++ or fortran, if appropriate). If you want to update the
bugzilla report, you can manually add a comment to it with the URL of
the patch submi
On 22/07/24 12:24 +0300, Ovidiu Panait wrote:
Hi,
When processing large header files, the C preprocessor reports error
on the wrong line.
This mailing list is for automated emails fom our bug tracker, not for
reporting bugs. Emails sent directly to this list will not get tracked
as bugs, and
Hi,
This mailing list is for automated mails from our bug database, not
for reporting bugs. Please see https://gcc.gnu.org/bugs/ for how to
report bugs, although it looks like this was already reported as Bug
115399.
Thanks for finding the bug though.
This mailing list is for automated mail from our bugzilla database,
not for reporting bugs. It looks like you should be using the gcc-help
mailing list anyway, not reporting a bug. I've CC'd that list. Please
remove the gcc-bugs mailing list from the CC list when replying.
On 20/05/24 20:48 +
This mailing list is for automated emails from our bug database, not
for reporting bugs directly.
See https://gcc.gnu.org/bugs/ for how to report bugs, thanks.
This mailing list is for automated email from our Bugzilla bug
database, not for reporting bugs directly.
Please see https://gcc.gnu.org/bugs/ for instructions on how to report
bugs.
However, Andrew already explained why GCC is correct and this is not a
GCC bug. Just use DECLARE_SINGLETON(Receive
This mailing list is for automated email from our bug tracker, it's
not for reporting bugs directly. Emails sent to this list are likely
to be missed, and definitely won't get entered into the bug tracker.
Please use Bugzilla to report bugs, as described at https://gcc.gnu.org/bugs/
> Not sure if this is the right mailing list for this.
It's not. This mailing list is for automated email from our bug
tracker. If you want to report a bug, please use that bug tracker
instead of an email.
See https://gcc.gnu.org/bugs/ for instructions.
Thanks!
On 18/05/23 12:01 +0100, Jonathan Wakely wrote:
This mailing list is for automated email from our bugzilla database.
To report a bug, please don't email the list, use bugzilla as
documented at https://gcc.gnu.org/bugs/ - thanks.
Note however, that GCC 9 is no longer supported by gcc.gnu.org, a
This mailing list is for automated email from our bugzilla database.
To report a bug, please don't email the list, use bugzilla as
documented at https://gcc.gnu.org/bugs/ - thanks.
This mailing list is for automated mails from our Bugzilla bug tracker
system.
If you want to report a bug, please see https://gcc.gnu.org/bugs/
If you want to ask a question, use the gcc-h...@gcc.gnu.org list, not
the gcc-bugs list. Please direct any follow-up discussion there
instead.
There is
On Fri, 5 May 2023 at 12:13, Florian Weimer wrote:
>
> * Puneet Kumar Yatnal via Gcc-bugs:
>
> > What is next step here? How do I post this in Bugzilla and get
> > support.
>
> This issue has already been fixed with this commit:
>
> commit 80fe172ba9820199c2bbce5d0611ffca27823049
> Author: Jonatha
The gcc-bugs@gcc.gnu.org list is for automated email from our Bugzilla
database, please don't use it to report bugs or to ask questions about
how GCC works.
For questions about using GCC send email to gcc-h...@gcc.gnu.org and
to report bugs please use bugzilla: https://gcc.gnu.org/bugs/
Thanks!
On Mon, 17 Apr 2023, 09:27 Puneet Kumar Yatnal (QUIC), <
quic_pune...@quicinc.com> wrote:
> Here issue is weakref symbol in gcc not using the __asm_ function pointed
> by pthread.h instead its calling directly ___pthread_cond_timedwait which
> is exposed by version_symbol in pthread_cond_wait.c of
On Mon, 17 Apr 2023, 07:54 Andrew Pinski via Gcc-help,
wrote:
> On Sun, Apr 16, 2023 at 10:41 PM Puneet Kumar Yatnal (QUIC) via
> Gcc-bugs wrote:
> >
> >
> > ++
> > From: Puneet Kumar Yatnal (QUIC)
> > Sent: Monday, April 17, 2023 9:26 AM
> > To: gcc-h...@gcc.gnu.org
> > Subject: Y2038: GCC gthr
Hello,
This mailing list is for automated mail from Bugzilla. Emails sent
directly to this list are liable to be missed or just ignored.
Please report bugs to Bugzilla instead, see https://gcc.gnu.org/bugs/
Patches should be sent to the gcc-patches mailing list, not gcc-bugs:
https://gcc.gnu.org
This mailing list is for automated emails from our bugzilla database,
not for reporting bugs directly.
To report a bug please follow the instructions at
https://gcc.gnu.org/bugs/
Your email doesn't look like a bug report anyway, maybe you meant to
send it to the gcc-help mailing list?
Thanks.
> The libiberty README says to report bugs to gcc-bugs@gcc.gnu.org.
Well that needs to be fixed. It should point to
https://gcc.gnu.org/bugs/ instead.
In GCC's bugzilla. You could also report it to the sourceware.org
bugzilla for binutils, but I think GCC is the upstream for libiberty.
The gcc-bugs mailing list is for automated mails from our Bugzilla
database. Bug reports should be entered into Bugzilla, and discussions
should happen in Bugzilla or on a more apppropriate mailing list
(because most GCC devs do not routinely read the gcc-bugs mails).
This mailing list is for automated mails from our bug database. Please
use the gcc-help mailing list for questions like this.
> I'm not sure if this is the right mailing list for asking about
No it's not, this list is for automated mails from our bug database.
> (possible) g++ issues. If not, I'd appreciate it if someone can point
> me to the right one.
See https://gcc.gnu.org/lists.html which tells you that gcc-help i
> These are the “true” ice-on-invalid-code bugs, i.e. those that are
> meant to be classified as “ice-on-invalid-code” instead of “error-recovery”
> in bugzilla. They generally get much more attention than “error-recovery”
> bugs.
And even those are lower priority than ice-on-valid bugs, and IMHO
> I am sorry maybe I send this in a wrong place, I have sent this again in
> gcc-bug-requ...@gcc.gun.org.
Well that's even more wrong. g...@gcc.gnu.org would be the right place.
I know you've realised the problem here now, but ...
This mailing list is for automated mails from our bugzilla database.
To report a bug please use bugzilla. Sending email directly to the
list will often be ignored, and will never create a bugzilla report.
See https://gcc.gnu.org/bugs/ for detai
27 matches
Mail list logo
