[Bug c++/119094] gcc uses all memory in recursive calls with increasingly complex templates

2025-03-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119094 --- Comment #1 from Andrew Pinski --- This might be a dup.

[Bug c++/119094] New: gcc uses all memory in recursive calls with increasingly complex templates

2025-03-02 Thread sandberg.sven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119094 Bug ID: 119094 Summary: gcc uses all memory in recursive calls with increasingly complex templates Product: gcc Version: 14.2.0 Status: UNCONFIRMED Severity: n

[Bug target/119084] LoongArch: __builtin_lsx_vldx can be incorrectly reordered

2025-03-02 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119084 --- Comment #6 from Xi Ruoyao --- https://gcc.gnu.org/pipermail/gcc-patches/2025-March/676725.html

[Bug target/119084] LoongArch: __builtin_lsx_vldx can be incorrectly reordered

2025-03-02 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119084 Xi Ruoyao changed: What|Removed |Added See Also||https://github.com/cisco/op

[Bug ipa/119093] New: ICE: in function_and_variable_visibility, at ipa-visibility.cc:715

2025-03-02 Thread bic60176 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119093 Bug ID: 119093 Summary: ICE: in function_and_variable_visibility, at ipa-visibility.cc:715 Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug target/106585] RISC-V: Miss optimization with code gen for zbs

2025-03-02 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106585 Xi Ruoyao changed: What|Removed |Added Summary|RISC-V: Mis-optimized code |RISC-V: Miss optimization

[Bug libstdc++/119081] libstdc++.modules.json generated with incorrect relative path if configured with '--prefix=/' or '--prefix=' (empty)

2025-03-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119081 --- Comment #4 from Andrew Pinski --- (In reply to Cyano Hao from comment #3) > Empty prefix can be used to avoid hard-coded absolute paths so compilers can > be copied/moved anywhere. GCC has relocation support in it and has since at least 201

[Bug libstdc++/119081] libstdc++.modules.json generated with incorrect relative path if configured with '--prefix=/' or '--prefix=' (empty)

2025-03-02 Thread c at cyano dot cn via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119081 --- Comment #3 from Cyano Hao --- Empty prefix can be used to avoid hard-coded absolute paths so compilers can be copied/moved anywhere. I recently learned it from the musl-cross-make project [1]. I plan to build GCC 15 using this method and bu

[Bug target/106585] RISC-V: Mis-optimized code gen for zbs

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106585 --- Comment #13 from Jeffrey A. Law --- Yea, I definitely explored the ext-dce approach before for a different testcase. But I think it's really the only viable path I see. A quick POC results in: bclra0,a0,a1# 12[c=4

[Bug target/119083] Remove SSE_FIRST_REG from ix86_class_likely_spilled_p

2025-03-02 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119083 --- Comment #6 from H.J. Lu --- (In reply to H.J. Lu from comment #4) > (In reply to Uroš Bizjak from comment #1) > > SSE_FIRST_REG is in ic86_class_likely_spilled_p because it is a > > single-member class. It is there because of SSE4 pcmpistrm

[Bug middle-end/119092] Add support for clang/LLVM builtin __builtin_{reduce,elementwise}_*

2025-03-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119092 --- Comment #1 from Andrew Pinski --- There are a few use of __builtin_elementwise_* out in the wild located here: https://github.com/IntroversionSoftware/gamelibs-glm/blob/8d4127ef32e05cec543d72680f781ebfd01052d1/glm/simd/common.h#L331 https:/

[Bug middle-end/119092] Add support for clang/LLVM builtin __builtin_{reduce,elementwise}_*

2025-03-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119092 --- Comment #2 from Andrew Pinski --- https://github.com/can1357/xstd/blob/c954497bb8542d451886363b52489615a21c4a68/includes/xstd/math.hpp#L666 uses it too. Though I think its usage is also semi questionable.

[Bug middle-end/119092] New: Add support for clang/LLVM builtin __builtin_{reduce,elementwise}_*

2025-03-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119092 Bug ID: 119092 Summary: Add support for clang/LLVM builtin __builtin_{reduce,elementwise}_* Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: enhancemen

[Bug target/106585] RISC-V: Mis-optimized code gen for zbs

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106585 --- Comment #12 from Jeffrey A. Law --- Looking at this again after nearly 2 years. At ud-dce things are actually not in bad shape: (insn 7 4 8 2 (set (reg:SI 141) (const_int 1 [0x1])) "j.c":2:20 278 {*movsi_internal} (nil)) (insn

[Bug target/119084] LoongArch: __builtin_lsx_vldx can be incorrectly reordered

2025-03-02 Thread chenglulu at loongson dot cn via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119084 --- Comment #4 from chenglulu --- This is indeed a significant issue. The operation of loading memory does not indicate that it is operating on memory.

[Bug tree-optimization/89967] Inefficient code generation for vld2q_lane_u8 under aarch64

2025-03-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89967 --- Comment #9 from Andrew Pinski --- (In reply to Andrew Pinski from comment #8) > There is also a missing clobber; let me file a bug for that ... It might not matter so I am not filing a bug right now.

[Bug target/118996] Should TARGET_SMALL_REGISTER_CLASSES_FOR_MODE_P return false for x86-64?

2025-03-02 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118996 --- Comment #15 from H.J. Lu --- (In reply to Hongtao Liu from comment #14) > (In reply to H.J. Lu from comment #13) > > (In reply to H.J. Lu from comment #11) > > > Created attachment 60609 [details] > > > An untested patch > > > > Hongtao, do

[Bug rtl-optimization/110163] [14/15 Regression] Comparing against a constant string is inefficient on some targets

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110163 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/118996] Should TARGET_SMALL_REGISTER_CLASSES_FOR_MODE_P return false for x86-64?

2025-03-02 Thread liuhongt at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118996 --- Comment #14 from Hongtao Liu --- (In reply to H.J. Lu from comment #13) > (In reply to H.J. Lu from comment #11) > > Created attachment 60609 [details] > > An untested patch > > Hongtao, do you have SPEC CPU2017 data on this patch? I haven

[Bug target/111428] RISC-V vector: Flaky segfault in {min|max}val_char_{1|2}.f90

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111428 Jeffrey A. Law changed: What|Removed |Added Last reconfirmed||2025-03-03 Status|UNCONFIR

[Bug target/112651] RISC-V Vector new option -mvect-lmul required to force LMUL values (rather than --param=riscv-autovec-lmul to hint at values)

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112651 Jeffrey A. Law changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug target/119084] LoongArch: __builtin_lsx_vldx can be incorrectly reordered

2025-03-02 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119084 Xi Ruoyao changed: What|Removed |Added Attachment #60632|0 |1 is obsolete|

[Bug middle-end/114069] Type punning RISC-V and SVE vectors causes ICE at -O1

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114069 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/103433] ICE in convert_move, at expr.c:219

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103433 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug middle-end/114069] Type punning RISC-V and SVE vectors causes ICE at -O1

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114069 Bug 114069 depends on bug 103433, which changed state. Bug 103433 Summary: ICE in convert_move, at expr.c:219 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103433 What|Removed |Added

[Bug target/118996] Should TARGET_SMALL_REGISTER_CLASSES_FOR_MODE_P return false for x86-64?

2025-03-02 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118996 --- Comment #13 from H.J. Lu --- (In reply to H.J. Lu from comment #11) > Created attachment 60609 [details] > An untested patch Hongtao, do you have SPEC CPU2017 data on this patch?

[Bug target/119084] LoongArch: __builtin_lsx_vldx can be incorrectly reordered

2025-03-02 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119084 --- Comment #2 from Xi Ruoyao --- (In reply to Xi Ruoyao from comment #1) > Created attachment 60632 [details] > untested patch It causes an ICE with V16QI y = __builtin_lsx_vldx ((char *)0, t); I'll fix it before sending the patch.

[Bug target/115322] SPEC2006 403.gcc internal error

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115322 --- Comment #3 from Jeffrey A. Law --- Unfortunately, you're likely going to have to do much of the debugging yourself. spec2k6 is licensed software that everyone does not have access to. What I would recommend would be to use qemu's remote de

[Bug target/119083] Remove SSE_FIRST_REG from ix86_class_likely_spilled_p

2025-03-02 Thread liuhongt at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119083 --- Comment #5 from Hongtao Liu --- (In reply to H.J. Lu from comment #3) > Created attachment 60640 [details] > A patch to remove SSE_FIRST_REG from ix86_class_likely_spilled_p > > Hongtao, can you measure its impact on SPEC CPU2017? Sure.

[Bug target/118931] [15 Regression] RISC-V: rv64gcv miscompile at -O[23] since r15-3228-g771256bcb9d

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118931 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/119083] Remove SSE_FIRST_REG from ix86_class_likely_spilled_p

2025-03-02 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119083 H.J. Lu changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug target/119083] Remove SSE_FIRST_REG from ix86_class_likely_spilled_p

2025-03-02 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119083 --- Comment #3 from H.J. Lu --- Created attachment 60640 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60640&action=edit A patch to remove SSE_FIRST_REG from ix86_class_likely_spilled_p Hongtao, can you measure its impact on SPEC CPU2017

[Bug rtl-optimization/117186] [12/13 Regression] aarch64 wrong code for (a < b) < (b < a)

2025-03-02 Thread powerboat9.gamer at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117186 Owen A. changed: What|Removed |Added CC||powerboat9.gamer at gmail dot com --- Commen

[Bug d/116975] Implement STAGE1_GDCFLAGS

2025-03-02 Thread ibuclaw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116975 Iain Buclaw changed: What|Removed |Added Attachment #60637|0 |1 is obsolete|

[Bug target/113739] ICE: in riscv_hard_regno_nregs, at config/riscv/riscv.cc:8072 with __attribute__((__target__("arch=rv64gcv")))

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113739 Jeffrey A. Law changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIR

[Bug target/113112] RISC-V: Dynamic LMUL feature stabilization for GCC-14 release

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113112 Jeffrey A. Law changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug ipa/119012] [riscv] Bootstrap comparison failure: gcc/rust/rust-lex.o differs

2025-03-02 Thread rsworktech at outlook dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119012 --- Comment #13 from Levi Zim --- Our full gcc 14.2.1+r753+g1cd744a6828f toolchain could bootstrap with 3228df20cfa3581015dc32657eb17d6f24af3104 reverted.

[Bug target/118146] [14 Regression] ICE: in riscv_legitimize_move, at config/riscv/riscv.cc:3641 when reinterpreting short vector as _Float16

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118146 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug rtl-optimization/116560] [13/14/15 Regression] RISC-V : rv32 code optimization , big code difference between 8/9.x and 10.x

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116560 --- Comment #2 from Jeffrey A. Law --- So at first glance it appears the bswap pass is kicking in and trying to improve this code. Essentially it wants to do a single 16bit load out of memory, rotate right by 8 bits and store. All that seems

[Bug target/109416] Missed constant propagation cases after reload

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109416 --- Comment #4 from Jeffrey A. Law --- So the issue here is the rv32 support for 64bit moves is kind of lame. Someone would need to adjust riscv_split_doubleword_move to account for handling (const_int 0) for the upper/lower half better. Secon

[Bug target/109279] RISC-V: complex constants synthesized should be improved

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109279 Jeffrey A. Law changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug target/119091] New: RISC-V eliminate redundancies in constant synthesis

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119091 Bug ID: 119091 Summary: RISC-V eliminate redundancies in constant synthesis Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Comp

[Bug libstdc++/119075] LWG4140 seems incompletely implemented

2025-03-02 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119075 --- Comment #5 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #3) > You can construct a contrived testcase that fails the same way due to the > _Bit_reference(_Bit_type*, _Bit_type) constructor: > > #include > #include >

[Bug target/109279] RISC-V: complex constants synthesized should be improved

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109279 --- Comment #23 from Jeffrey A. Law --- This has devolved into a bit of a mess. If we look at the repeating sequence in the original report we get: li a5,16842752 addia5,a5,257 sllia0,a5,32 add

[Bug libstdc++/119075] LWG4140 seems incompletely implemented

2025-03-02 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119075 --- Comment #4 from Jonathan Wakely --- (In reply to Andrew Pinski from comment #1) > Reading pr 115098 seems to this on purpose. It was, but I can't find where we use that default constructor now. Maybe it can be removed now. That doesn't chan

[Bug libstdc++/119089] FAIL: 23_containers/vector/debug/assign4_backtrace_neg.cc -std=gnu++17 (test for excess errors)

2025-03-02 Thread danglin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119089 --- Comment #8 from John David Anglin --- (In reply to Jonathan Wakely from comment #5) > Isn't this a glibc change, and you need to regenerate the gcc fixincludes > headers after updating glibc? That could have happened. Will investigate. Th

[Bug libstdc++/119089] FAIL: 23_containers/vector/debug/assign4_backtrace_neg.cc -std=gnu++17 (test for excess errors)

2025-03-02 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119089 --- Comment #7 from Jonathan Wakely --- Or https://sourceware.org/bugzilla/show_bug.cgi?id=32621 rather

[Bug libstdc++/119089] FAIL: 23_containers/vector/debug/assign4_backtrace_neg.cc -std=gnu++17 (test for excess errors)

2025-03-02 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119089 --- Comment #6 from Jonathan Wakely --- https://sourceware.org/bugzilla/show_bug.cgi?id=32625

[Bug libstdc++/119089] FAIL: 23_containers/vector/debug/assign4_backtrace_neg.cc -std=gnu++17 (test for excess errors)

2025-03-02 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119089 --- Comment #5 from Jonathan Wakely --- Isn't this a glibc change, and you need to regenerate the gcc fixincludes headers after updating glibc?

[Bug libstdc++/119075] LWG4140 seems incompletely implemented

2025-03-02 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119075 --- Comment #3 from Jonathan Wakely --- You can construct a contrived testcase that fails the same way due to the _Bit_reference(_Bit_type*, _Bit_type) constructor: #include #include struct X { X(int, int) { } }; int test2(std::vector::refe

[Bug target/119090] [MAME] [Model 1] 3D graphics are full of glitches if built with CXXFLAGS="-march=native -mtune=native"

2025-03-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119090 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug libstdc++/119081] libstdc++.modules.json generated with incorrect relative path if configured with '--prefix=/' or '--prefix=' (empty)

2025-03-02 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119081 --- Comment #2 from Jonathan Wakely --- In theory you could want /bin/gcc and /include/c++/15.0.0/* and /lib64/libgcc_s.so ... but I don't see why anybody would.

[Bug libstdc++/119075] LWG4140 seems incompletely implemented

2025-03-02 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119075 --- Comment #2 from Jonathan Wakely --- I think [member.functions] allows us to define private constructors. The test case above seems extremely contrived and unlikely to reflect any real code.

[Bug c++/119090] New: [MAME] [Model 1] 3D graphics are full of glitches if built with CXXFLAGS="-march=native -mtune=native"

2025-03-02 Thread redwindwanderer at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119090 Bug ID: 119090 Summary: [MAME] [Model 1] 3D graphics are full of glitches if built with CXXFLAGS="-march=native -mtune=native" Product: gcc Version: 14.2.0 Status: UNCON

[Bug testsuite/111969] RISC-V rv32gcv: 12 grouped flaky failures

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111969 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/89967] Inefficient code generation for vld2q_lane_u8 under aarch64

2025-03-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89967 --- Comment #8 from Andrew Pinski --- There is also a missing clobber; let me file a bug for that ...

[Bug target/116720] [13/14 Regression] RISC-V: Unrecognizable insn with xtheadmemidx on rv32

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116720 Jeffrey A. Law changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/116720] [13/14 Regression] RISC-V: Unrecognizable insn with xtheadmemidx on rv32

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116720 --- Comment #5 from GCC Commits --- The releases/gcc-13 branch has been updated by Jeff Law : https://gcc.gnu.org/g:e00c33df5d64990197b2382399a2a8b80b994176 commit r13-9406-ge00c33df5d64990197b2382399a2a8b80b994176 Author: Jeff Law Date: Su

[Bug target/116720] [13/14 Regression] RISC-V: Unrecognizable insn with xtheadmemidx on rv32

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116720 --- Comment #4 from GCC Commits --- The releases/gcc-14 branch has been updated by Jeff Law : https://gcc.gnu.org/g:c1535f242f703d3142bef1ca7c31d1ee17633696 commit r14-11371-gc1535f242f703d3142bef1ca7c31d1ee17633696 Author: Jeff Law Date: S

[Bug libstdc++/119089] FAIL: 23_containers/vector/debug/assign4_backtrace_neg.cc -std=gnu++17 (test for excess errors)

2025-03-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119089 --- Comment #4 from Andrew Pinski --- (In reply to John David Anglin from comment #3) > Maybe introduced by the following change: > https://gcc.gnu.org/git/?p=gcc.git;a=commit; > h=ad2908ed4ec5eff3cad3fd142cde5c1fac4788e9 I doubt it since the c

[Bug target/115010] m68k: invalid subl instruction generated

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010 Jeffrey A. Law changed: What|Removed |Added Last reconfirmed|2024-05-09 00:00:00 |2025-03-02 Status|UNCONFIR

[Bug target/110188] gcc for RISC-V stack aligned error

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110188 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/119089] FAIL: 23_containers/vector/debug/assign4_backtrace_neg.cc -std=gnu++17 (test for excess errors)

2025-03-02 Thread danglin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119089 --- Comment #3 from John David Anglin --- Maybe introduced by the following change: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=ad2908ed4ec5eff3cad3fd142cde5c1fac4788e9

[Bug fortran/101577] [Interop] TYPE with BIND(C): Reject empty TYPE with zero components

2025-03-02 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101577 anlauf at gcc dot gnu.org changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot gnu

[Bug target/88589] ICE + seemingly wrong codegen with m68k-elf

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88589 Jeffrey A. Law changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug libstdc++/119089] FAIL: 23_containers/vector/debug/assign4_backtrace_neg.cc -std=gnu++17 (test for excess errors)

2025-03-02 Thread danglin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119089 --- Comment #2 from John David Anglin --- Don't know. It's defined in generic code. All the initializers seem to have an extra set of `{}`.

[Bug target/96532] [m68k] gcc 10.x generates calls to memset even for very small amounts

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96532 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/119089] FAIL: 23_containers/vector/debug/assign4_backtrace_neg.cc -std=gnu++17 (test for excess errors)

2025-03-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119089 --- Comment #1 from Andrew Pinski --- Note I do think this is a glibc issue but we should be able to work around it here too. I wonder why PTHREAD_COND_INITIALIZER has an extra set of `{}` on it. Removing that and it works.

[Bug target/98382] [m68k] ICE: in output_move_qimode, at config/m68k/m68k.c:3284 when building webkit2gtk

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98382 Jeffrey A. Law changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRM

[Bug c/119089] New: FAIL: 23_containers/vector/debug/assign4_backtrace_neg.cc -std=gnu++17 (test for excess errors)

2025-03-02 Thread danglin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119089 Bug ID: 119089 Summary: FAIL: 23_containers/vector/debug/assign4_backtrace_neg.cc -std=gnu++17 (test for excess errors) Product: gcc Version: 15.0 St

[Bug d/116975] Implement STAGE1_GDCFLAGS

2025-03-02 Thread ibuclaw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116975 --- Comment #1 from Iain Buclaw --- Created attachment 60637 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60637&action=edit First attempt at PR116975 Making a stab at this. As it's done in toplevel Makefile.tpl, it generates STAGExxx_GD

[Bug target/70557] uint64_t zeroing on 32-bit hardware

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70557 --- Comment #11 from Jeffrey A. Law --- Siarhei, it's fine to attach potential patches to bugzilla entries, but once you're ready for them to be reviewed and potentially integrated, they really need to be posted to gcc-patches. They are highly

[Bug testsuite/52641] Test cases fail for 16-bit int targets

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52641 Jeffrey A. Law changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug libffi/47248] libffi build failure with ld.gold (works with trunk 20110106, fails with 20110110)

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47248 Jeffrey A. Law changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug driver/43090] Why gcc can't invoke -as and uses 'as' instead?

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43090 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/118538] throw not caught causing an seg fault rather than a `terminate called after throwing an instance of 'int'` message

2025-03-02 Thread disservin.social at gmail dot com via Gcc-bugs
ble-multilib --enable-default-pie Thread model: posix Supported LTO compression algorithms: zlib gcc version 15.0.1 20250302 (experimental) (GCC) ➜ ~ /usr/local/bin/g++ -O0 -std=c++17 -Wall -Wextra -Wpedantic -Wuninitialized -fno-strict-aliasing -fwrapv -g3 gcc-bug.cpp && ./a.out gcc-b

[Bug libffi/28036] libffi executable stack (missing .note.GNU-stack on .o files)

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28036 Jeffrey A. Law changed: What|Removed |Added Resolution|--- |INVALID Status|NEW

[Bug target/118934] [15 Regression] RISC-V: ICE: output_operand: invalid expression as operand

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118934 Jeffrey A. Law changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/118934] [15 Regression] RISC-V: ICE: output_operand: invalid expression as operand

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118934 --- Comment #3 from GCC Commits --- The master branch has been updated by Jeff Law : https://gcc.gnu.org/g:67e824c2497176980cb0c5d14bc730fa4ce2e1ad commit r15-7787-g67e824c2497176980cb0c5d14bc730fa4ce2e1ad Author: Jeff Law Date: Sun Mar 2 1

[Bug modula2/119088] ICE when for loop accesses an unknown variable as the iterator

2025-03-02 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119088 Gaius Mulley changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug modula2/119088] ICE when for loop accesses an unknown variable as the iterator

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119088 --- Comment #3 from GCC Commits --- The master branch has been updated by Gaius Mulley : https://gcc.gnu.org/g:585aa4065f1028c2fbfab55462e5e5e6b3c208c4 commit r15-7786-g585aa4065f1028c2fbfab55462e5e5e6b3c208c4 Author: Gaius Mulley Date: Sun

[Bug tree-optimization/90697] ia64: segmentation fault during GIMPLE pass: dom

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90697 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/53947] [meta-bug] vectorizer missed-optimizations

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947 Bug 53947 depends on bug 49513, which changed state. Bug 49513 Summary: DOM inhibits if-conversion and vectorization https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49513 What|Removed |Added ---

[Bug tree-optimization/49513] DOM inhibits if-conversion and vectorization

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49513 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/89078] [meta-bug] Improve the gfortran manual

2025-03-02 Thread sandra at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89078 Bug 89078 depends on bug 47928, which changed state. Bug 47928 Summary: Gfortran intrinsics documentation paragraph ordering illogical https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47928 What|Removed |Added

[Bug fortran/47928] Gfortran intrinsics documentation paragraph ordering illogical

2025-03-02 Thread sandra at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47928 sandra at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|-

[Bug fortran/47928] Gfortran intrinsics documentation paragraph ordering illogical

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47928 --- Comment #9 from GCC Commits --- The master branch has been updated by Sandra Loosemore : https://gcc.gnu.org/g:43f2bc4aee3f1302e70e41c23770e6fcca4ff5fc commit r15-7784-g43f2bc4aee3f1302e70e41c23770e6fcca4ff5fc Author: Sandra Loosemore Date

[Bug fortran/47928] Gfortran intrinsics documentation paragraph ordering illogical

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47928 --- Comment #7 from GCC Commits --- The master branch has been updated by Sandra Loosemore : https://gcc.gnu.org/g:1f458cfc17775903ab85bda127d0454014f70906 commit r15-7782-g1f458cfc17775903ab85bda127d0454014f70906 Author: Sandra Loosemore Date

[Bug fortran/47928] Gfortran intrinsics documentation paragraph ordering illogical

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47928 --- Comment #8 from GCC Commits --- The master branch has been updated by Sandra Loosemore : https://gcc.gnu.org/g:9edd165ea897b49946f68eebeac160f4c55b29b6 commit r15-7783-g9edd165ea897b49946f68eebeac160f4c55b29b6 Author: Sandra Loosemore Date

[Bug fortran/47928] Gfortran intrinsics documentation paragraph ordering illogical

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47928 --- Comment #6 from GCC Commits --- The master branch has been updated by Sandra Loosemore : https://gcc.gnu.org/g:d8f5e1b0ba01ac65dbae98daa065109f18b87751 commit r15-7781-gd8f5e1b0ba01ac65dbae98daa065109f18b87751 Author: Sandra Loosemore Date

[Bug modula2/119088] ICE when for loop accesses an unknown variable as the iterator

2025-03-02 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119088 --- Comment #2 from Gaius Mulley --- Created attachment 60636 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60636&action=edit Proposed fix detecting unknown variable in variable analysis Proposed fix which detects a variable with an unkn

[Bug d/116961] [12/13/14 regression] Valgrind reports uninitialized memory use in dstruct.d (dmd.dstruct._isZeroInit(dmd.expression.Expression))

2025-03-02 Thread ibuclaw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116961 Iain Buclaw changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug d/118802] [15 regression] Bootstrap comparison failure on libphobos/libdruntime/core/internal/gc/impl/conservative/gc.o since r15-7400-gd3ff498c478ace

2025-03-02 Thread ibuclaw at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118802 Bug 118802 depends on bug 116961, which changed state. Bug 116961 Summary: [12/13/14 regression] Valgrind reports uninitialized memory use in dstruct.d (dmd.dstruct._isZeroInit(dmd.expression.Expression)) https://gcc.gnu.org/bugzilla/show_bug.cg

[Bug d/116961] [12/13/14 regression] Valgrind reports uninitialized memory use in dstruct.d (dmd.dstruct._isZeroInit(dmd.expression.Expression))

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116961 --- Comment #15 from GCC Commits --- The releases/gcc-12 branch has been updated by Iain Buclaw : https://gcc.gnu.org/g:f6be26657c8b974a5caf39350e4965cfb2c4b936 commit r12-10972-gf6be26657c8b974a5caf39350e4965cfb2c4b936 Author: Iain Buclaw Da

[Bug d/116961] [12/13/14 regression] Valgrind reports uninitialized memory use in dstruct.d (dmd.dstruct._isZeroInit(dmd.expression.Expression))

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116961 --- Comment #14 from GCC Commits --- The releases/gcc-13 branch has been updated by Iain Buclaw : https://gcc.gnu.org/g:21b3e23bd972544c1e2f704e8b05dd9252a288ce commit r13-9405-g21b3e23bd972544c1e2f704e8b05dd9252a288ce Author: Iain Buclaw Dat

[Bug d/116961] [12/13/14 regression] Valgrind reports uninitialized memory use in dstruct.d (dmd.dstruct._isZeroInit(dmd.expression.Expression))

2025-03-02 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116961 --- Comment #13 from GCC Commits --- The releases/gcc-14 branch has been updated by Iain Buclaw : https://gcc.gnu.org/g:04b5c8b90cd95611d99684282cc321f06a0b49c2 commit r14-11370-g04b5c8b90cd95611d99684282cc321f06a0b49c2 Author: Iain Buclaw Da

[Bug target/118911] [15 Regression] bitfield-bitint-abi-align{8,16}.c fails on aarch64-linux-gnu since r15-268

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118911 Jeffrey A. Law changed: What|Removed |Added Priority|P3 |P2

[Bug modula2/119088] ICE when for loop accesses an unknown variable as the iterator

2025-03-02 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119088 Gaius Mulley changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug modula2/119088] New: ICE when for loop accesses an unknown variable as the iterator

2025-03-02 Thread gaius at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119088 Bug ID: 119088 Summary: ICE when for loop accesses an unknown variable as the iterator Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug target/118959] [15 Regression] 5-14% slowdown of 400.perlbench since r15-7400-gd3ff498c478ace

2025-03-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118959 Jeffrey A. Law changed: What|Removed |Added Priority|P3 |P2

  1   2   >