[Bug preprocessor/119753] New: gcc -E is not POSIX-compliant

2025-04-12 Thread love4boobies at yahoo dot com via Gcc-bugs
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

[Bug ada/119643] replacement of Integer by Natural/Positive not ignored in subprogram renaming

2025-04-12 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
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

[Bug c++/113835] [13/14/15 Regression] compiling std::vector with const size in C++20 is slow

2025-04-12 Thread redi at gcc dot gnu.org via Gcc-bugs
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

[Bug ada/119643] replacement of Integer by Natural/Positive not ignored in subprogram renaming

2025-04-12 Thread ebotcazou at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119643 Eric Botcazou changed: What|Removed |Added Target Milestone|--- |15.0 Status|ASSIGNED

[Bug c++/113835] [13/14/15 Regression] compiling std::vector with const size in C++20 is slow

2025-04-12 Thread redi at gcc dot gnu.org via Gcc-bugs
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.

[Bug bootstrap/119729] configure should issue a warning about building in the src tree

2025-04-12 Thread mcccs at gmx dot com via Gcc-bugs
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

[Bug modula2/119751] There's a need to tidy up m2 subdirectories' contents

2025-04-12 Thread sjames at gcc dot gnu.org via Gcc-bugs
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.

[Bug d/119758] New: d: -fonly= argument only matches when including full relative path to the input file

2025-04-12 Thread ibuclaw at gcc dot gnu.org via Gcc-bugs
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

[Bug tree-optimization/119718] __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call

2025-04-12 Thread lucier at math dot purdue.edu via Gcc-bugs
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/

[Bug debug/119766] New: -gsplit-dwarf and -fdebug-types-section leads to multiple .debug_info.dwo sections

2025-04-12 Thread simon.marchi at polymtl dot ca via Gcc-bugs
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

[Bug target/119765] FAIL: gcc.target/i386/amd64-abi-9.c on Windows

2025-04-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
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.

[Bug debug/119766] -gsplit-dwarf and -fdebug-types-section leads to multiple .debug_info.dwo sections

2025-04-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
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 .

[Bug debug/119766] -gsplit-dwarf and -fdebug-types-section leads to multiple .debug_info.dwo sections

2025-04-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119766 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c/119765] New: FAIL: gcc.target/i386/amd64-abi-9.c on Windows

2025-04-12 Thread nightstrike at gmail dot com via Gcc-bugs
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

[Bug c++/119755] type_traits:828:11: fatal error: failed to load pendings for 'std::__is_one_of'

2025-04-12 Thread nshead at gcc dot gnu.org via Gcc-bugs
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.

<    1   2