https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119753
Bug ID: 119753
Summary: gcc -E is not POSIX-compliant
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: preprocessor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119643
--- Comment #4 from GCC Commits ---
The master branch has been updated by Eric Botcazou :
https://gcc.gnu.org/g:ecef0d7c53d59a701bc09e2df8fbec5d4c61267a
commit r15-9394-gecef0d7c53d59a701bc09e2df8fbec5d4c61267a
Author: Eric Botcazou
Date: S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113835
--- Comment #12 from Jonathan Wakely ---
The __uninitialized_default_n_1 specialization assumes that we can use
std::fill_n to assign to objects outside their lifetime. I don't think that's
valid during constant evaluation, is it? That's why we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119643
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |15.0
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113835
--- Comment #13 from Jonathan Wakely ---
Hmm, __uninitialized_default doesn't have a std::is_constant_evaluated check,
but I think it needs it for exactly the same reasons.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119729
--- Comment #6 from mcccs at gmx dot com ---
I haven't been given a sourceware account, I can't file a bug on sourceware.
Maybe we can do it for GCC only and if they agree with it in the future they
can change it:
Updated patch:
+if test $srcdi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119751
--- Comment #9 from Sam James ---
(In reply to Zbigniew from comment #8)
That sounds like it belongs in a new bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119758
Bug ID: 119758
Summary: d: -fonly= argument only matches when including full
relative path to the input file
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Sev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119718
--- Comment #16 from lucier at math dot purdue.edu ---
I'm sorry, I don't understand how to get the information from the recent
changes
https://gcc.gnu.org/cgit/gcc/commit/?id=0562e17bd04b65aebff4721db05631b9f34af146
and
https://gcc.gnu.org/cgit/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119766
Bug ID: 119766
Summary: -gsplit-dwarf and -fdebug-types-section leads to
multiple .debug_info.dwo sections
Product: gcc
Version: unknown
Status: UNCONFIRMED
Se
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765
--- Comment #1 from Andrew Pinski ---
I suspect it is disable the test for windows abi. It is testing varargs setting
of eax for the number of use registers passed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119766
--- Comment #1 from Andrew Pinski ---
My reading of the documentation, that gcc is doing the correct thing here. You
requested that the types split into their own section and splitting it out to a
dwo file .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119766
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765
Bug ID: 119765
Summary: FAIL: gcc.target/i386/amd64-abi-9.c on Windows
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119755
--- Comment #5 from Nathaniel Shead ---
Created attachment 61091
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61091&action=edit
pr119755_patch
Patch I'm testing for this issue.
101 - 115 of 115 matches
Mail list logo