[Bug libstdc++/120325] [Regression] GCC-15 cannot build LLVM 20.1.5 with CMAKE_CXX_STANDARD=20

2025-05-18 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120325 --- Comment #2 from Jonathan Wakely --- I'll comment on github too, but I think the problem is that you're using -DCMAKE_CXX_STANDARD=20 It looks to me like LLVM's iterator facade is completely incompatible with C++20. The operator overloads li

[Bug tree-optimization/31313] consecutive strcmps are not merged

2025-05-18 Thread kaelfandrew at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31313 Kael Franco changed: What|Removed |Added CC||kaelfandrew at gmail dot com --- Comment #

[Bug tree-optimization/120331] match causes an extra assignment sometimes

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120331 --- Comment #7 from Andrew Pinski --- Patch posted: https://gcc.gnu.org/pipermail/gcc-patches/2025-May/683999.html There was no regressions with this version of the patch and the issue I found was solved too.

[Bug c++/120335] Defining a function return type allowed with -pedantic-errors with using statement

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120335 --- Comment #2 from Andrew Pinski --- Testcase: ``` using T = struct {}(); ```

[Bug target/120333] New: RISC-V: Wrong code with bitmanip extension

2025-05-18 Thread kristerw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120333 Bug ID: 120333 Summary: RISC-V: Wrong code with bitmanip extension Product: gcc Version: 16.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: targe

[Bug c++/120335] Defining a function return type allowed with -pedantic-errors with using statement

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120335 Andrew Pinski changed: What|Removed |Added Summary|Defining a function return |Defining a function return

[Bug lto/120334] New: lto plugin doesn't check for excess section size

2025-05-18 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120334 Bug ID: 120334 Summary: lto plugin doesn't check for excess section size Product: gcc Version: 16.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/119966] [16 regression] pru: Invalid register in RTL expression starting with r16-160-ge6f89d78c1a752

2025-05-18 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119966 --- Comment #9 from GCC Commits --- The master branch has been updated by Dimitar Dimitrov : https://gcc.gnu.org/g:eb2ea476db2182939f585df7d806225649ee4f62 commit r16-718-geb2ea476db2182939f585df7d806225649ee4f62 Author: Dimitar Dimitrov Date

[Bug rtl-optimization/120329] Combine temporarily creates paradoxical mem subregs for strict-alignment targets

2025-05-18 Thread dimitar at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120329 --- Comment #6 from Dimitar Dimitrov --- To reproduce after r16-718-geb2ea476db2182, apply the following change to tighten paradoxical subreg checks, and build libgcc for armv8l-unknown-linux-gnueabihf: - /* Do not allow normal SUBREG with str

[Bug c++/107953] Greater-than operator misparsed inside a lambda expression used as a template argument

2025-05-18 Thread ethanhancock at me dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107953 Ethan Hancock changed: What|Removed |Added CC||ethanhancock at me dot com --- Comment

[Bug rtl-optimization/120284] inline assembly operand constraint not comply with document

2025-05-18 Thread huiba.lhb--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120284 --- Comment #7 from Huiba Li --- > In that case you need to use "movq %1, %0" in the asm to actually copy the > value, because the constraints don't guarantee it is the same register, it > can very well be a different one. > By using "0" or "+r"

[Bug gcov-profile/120321] Inconsistent line coverage for "for(;;)" "while(1)" etc

2025-05-18 Thread wentaoz5 at illinois dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120321 --- Comment #1 from Wentao Zhang --- Another example that shows the effect can propagate from the "while(1)" line to adjacent no-code, reduced from https://sources.debian.org/src/lzo2/2.10-2/src/lzo1x_d.ch/#L98 where "NEED_IP" is expanded to "(

[Bug middle-end/120276] [16 Regression] ICE in partial_subreg_p with SVE

2025-05-18 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120276 --- Comment #3 from GCC Commits --- The master branch has been updated by Jennifer Schmitz : https://gcc.gnu.org/g:2ec5082dd24cef5149ba645ee88a9acd8b4c290a commit r16-727-g2ec5082dd24cef5149ba645ee88a9acd8b4c290a Author: Jennifer Schmitz Date

[Bug target/120344] New: code size increase with gcc 13 due to repeated loading of higher address in assembly for riscv

2025-05-18 Thread fanghuaqi at vip dot qq.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120344 Bug ID: 120344 Summary: code size increase with gcc 13 due to repeated loading of higher address in assembly for riscv Product: gcc Version: 14.2.1 Status: UNCONFIRMED

[Bug target/119847] [13/14/15 Regression] RISC-V:GCC fail to optimize repeated patterns in volatile operations

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119847 Andrew Pinski changed: What|Removed |Added CC||fanghuaqi at vip dot qq.com --- Comment

[Bug cobol/119331] cobol: unimplemented exceptions abort compilation - even if requested to NOT use them

2025-05-18 Thread jklowden at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119331 James K. Lowden changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug cobol/119771] FE (parser): CONSTANT AS LENGTH OF does not error - but result in length of zero

2025-05-18 Thread jklowden at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119771 James K. Lowden changed: What|Removed |Added Status|UNCONFIRMED |WAITING Ever confirmed|0

[Bug c++/120335] Defining a function return type allowed with -pedantic-errors with using statement

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120335 --- Comment #4 from Andrew Pinski --- (In reply to eczbek.void from comment #3) > This also has the same issue: > ``` > auto(*x)()->struct{}; > ``` That one fails for me as a parse error even without -pedantic: ``` :1:19: error: expected identi

[Bug c++/120336] New: internal compiler error: tree check: expected tree that contains 'decl minimal' structure, have 'error_mark' in decl_internal_context_p, at cp/tree.cc:3866 in trunk

2025-05-18 Thread mario.rodriguezb1 at um dot es via Gcc-bugs
ate struct mp::pair { }; ``` ``` /opt/compiler-explorer/gcc-trunk-20250518/include/c++/16.0.0/bits/stl_pair.h:338:7: internal compiler error: tree check: expected tree that contains 'decl minimal' structure, have 'error_mark' in decl_internal_context_p, at cp/tree.cc:3866

[Bug fortran/120099] [16 regression] gfortran.dg/specifics_1.f90 FAILs since r16-372-g064cac730f88dc

2025-05-18 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120099 --- Comment #21 from anlauf at gcc dot gnu.org --- Patch from comment#16 submitted: https://gcc.gnu.org/pipermail/fortran/2025-May/062180.html I hope I got the description of the issue right in the changelog.

[Bug ada/120106] replace hardcoded gnatmake commands with configuration variables

2025-05-18 Thread nicolas at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120106 Nicolas Boulenguez changed: What|Removed |Added Attachment #61305|0 |1 is obsolete|

[Bug c++/120338] New: internal compiler error: in expand_or_defer_fn_1, at cp/semantics.cc:5479 with main and delete since version 15.1

2025-05-18 Thread mario.rodriguezb1 at um dot es via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120338 Bug ID: 120338 Summary: internal compiler error: in expand_or_defer_fn_1, at cp/semantics.cc:5479 with main and delete since version 15.1 Product: gcc Version: 1

[Bug c++/120335] Defining a function return type allowed with -pedantic-errors with using statement

2025-05-18 Thread eczbek.void at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120335 --- Comment #3 from eczbek.void at gmail dot com --- This also has the same issue: ``` auto(*x)()->struct{}; ```

[Bug c++/120337] New: internal compiler error: error reporting routines re-entered. tuple library since version 14.1

2025-05-18 Thread mario.rodriguezb1 at um dot es via Gcc-bugs
::mutex m; public: void inc() { b++; } }; int main() { A a; std::thread t1(std::bind(&A::inc,std::ref(a)), a); t1.join(); } ``` Stack dump ``` /opt/compiler-explorer/gcc-trunk-20250518/include/c++/16.0.0/tuple:992:2: required by the constraints of 'template template

[Bug ada/120106] replace hardcoded gnatmake commands with configuration variables

2025-05-18 Thread nicolas at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120106 --- Comment #3 from Nicolas Boulenguez --- Created attachment 61463 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61463&action=edit GNATMAKE for host only, v02 v02 uses the host compiler set by ./configure in gnattools/Makefile.in and gc

[Bug c++/120339] New: internal compiler error: Segmentation fault diagnostic_impl since version 14.1

2025-05-18 Thread mario.rodriguezb1 at um dot es via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120339 Bug ID: 120339 Summary: internal compiler error: Segmentation fault diagnostic_impl since version 14.1 Product: gcc Version: 16.0 Status: UNCONFIRMED Severity:

[Bug target/120333] [16 Regression] RISC-V: Wrong code with bitmanip extension

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120333 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0

[Bug target/120333] [16 Regression] RISC-V: Wrong code with bitmanip extension

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120333 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |16.0 Summary|RISC-V: Wrong c

[Bug c++/120335] Defining a function return type allowed with -pedantic-errors with using statement

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120335 --- Comment #6 from Andrew Pinski --- (In reply to eczbek.void from comment #5) > it seems to compile here: https://godbolt.org/z/dq51b7E3o Oh inside a function, outside is not an issue. But I suspect that is a different issue dealing with tra

[Bug c++/120335] Defining a function return type allowed with -pedantic-errors with using statement

2025-05-18 Thread eczbek.void at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120335 --- Comment #5 from eczbek.void at gmail dot com --- it seems to compile here: https://godbolt.org/z/dq51b7E3o

[Bug c++/120335] Defining a function return type allowed with -pedantic-errors with using statement

2025-05-18 Thread eczbek.void at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120335 --- Comment #7 from eczbek.void at gmail dot com --- thanks!

[Bug c++/120340] New: Can define a struct type with a trailing return type on a function type as decl inside a function

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120340 Bug ID: 120340 Summary: Can define a struct type with a trailing return type on a function type as decl inside a function Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug tree-optimization/120341] New: wrong code at -O1 and above with "-fallow-store-data-races" on x86_64-linux-gnu

2025-05-18 Thread zhendong.su at inf dot ethz.ch via Gcc-bugs
-bootstrap --enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk --enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 16.0.0 20250518 (experimental) (GCC) [562] % [562] % gcctk -

[Bug c++/120335] Defining a function return type allowed with -pedantic-errors with using statement

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120335 --- Comment #8 from Andrew Pinski --- (In reply to Andrew Pinski from comment #6) > (In reply to eczbek.void from comment #5) > > it seems to compile here: https://godbolt.org/z/dq51b7E3o > > Oh inside a function, outside is not an issue. > >

[Bug tree-optimization/120342] New: wrong code at -O{s,2,3} with "-fno-tree-ccp -fno-tree-forwprop" on x86_64-linux-gnu

2025-05-18 Thread zhendong.su at inf dot ethz.ch via Gcc-bugs
-bootstrap --enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk --enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 16.0.0 20250518 (experimental) (GCC) [571] % [571] % gcctk -O3 sm

[Bug ada/114065] gnat build with -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64 fails on 32bit archs

2025-05-18 Thread nicolas at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114065 --- Comment #42 from Nicolas Boulenguez --- Created attachment 61464 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61464&action=edit v17 GNAT.Sockets.Thin_Common wrappers As suggested in https://inbox.sourceware.org/gcc-patches/aBZh8egJT

[Bug tree-optimization/120341] [15/16 Regregression] wrong code at -O1 and above with "-fallow-store-data-races" on x86_64-linux-gnu

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120341 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Summary|wrong code at -O

[Bug tree-optimization/120342] wrong code at -O{s,2,3} with "-fno-tree-ccp -fno-tree-forwprop" on x86_64-linux-gnu

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120342 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/120341] [15/16 Regregression] wrong code at -O1 and above with "-fallow-store-data-races" on x86_64-linux-gnu

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120341 --- Comment #2 from Andrew Pinski --- ``` DECL_P (base) && TREE_READONLY (base) ``` Maybe that should be: (TREE_CODE (base) == STRING_CST || (DECL_P (base) TREE_READONLY (base))) Or some helper function which does the same.

[Bug tree-optimization/120342] wrong code at -O{s,2,3} with "-fno-tree-ccp -fno-tree-forwprop" on x86_64-linux-gnu

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120342 --- Comment #2 from Andrew Pinski --- (In reply to Andrew Pinski from comment #1) > This is an aliasing violation. > > You write to p via int and then again via the struct and then read it back > via int. I should say write partially via the s

[Bug c++/120343] New: inconvenient order of error messages

2025-05-18 Thread f.heckenbach--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120343 Bug ID: 120343 Summary: inconvenient order of error messages Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/120343] inconvenient order of error messages

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120343 --- Comment #1 from Andrew Pinski --- Hmm, clang even has a similar issue in their diagnostic.

[Bug c++/120343] inconvenient order of error messages

2025-05-18 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120343 --- Comment #2 from Andrew Pinski --- Only MSVC (which is usually bad when it comes to diagnostic issues) actually does a decent job at providing the good diagnostic here: (4): error C2187: syntax error: ']' was unexpected here (2): fatal error

[Bug c++/120335] New: Defining a function return type allowed with -pedantic-errors

2025-05-18 Thread eczbek.void at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120335 Bug ID: 120335 Summary: Defining a function return type allowed with -pedantic-errors Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal