[Bug c++/115695] New: spurious warning for -Wsign-compare with c++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115695 Bug ID: 115695 Summary: spurious warning for -Wsign-compare with c++ Product: gcc Version: 14.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug tree-optimization/115652] [15 Regression] GCN: FAIL: gcc.dg/vect/pr70138-{1,2}.c (internal compiler error: verify_ssa failed)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115652 Thomas Schwinge changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Bug bootstrap/115635] [15 regression] Bootstrap fails with failed self-test with the rust fe (diagnostic-path.cc:1153: test_empty_path: FAIL: ASSERT_FALSE ((path.interprocedural_p ()))) since r15-159

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115635 --- Comment #12 from Evgeny Karpov --- Could you please confirm that the patch resolves the issue?

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #13 from Evgeny Karpov --- Could you please confirm that the patch resolves the issue?

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #14 from cqwrteur --- (In reply to Evgeny Karpov from comment #13) > Could you please confirm that the patch resolves the issue? why should I? As a microsoft sholder i would say fuck you for using gmail and google bs

[Bug bootstrap/115635] [15 regression] Bootstrap fails with failed self-test with the rust fe (diagnostic-path.cc:1153: test_empty_path: FAIL: ASSERT_FALSE ((path.interprocedural_p ()))) since r15-159

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115635 --- Comment #13 from Sam James --- Hi Evgeny, I tested your patch last night and it works.

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #15 from cqwrteur --- (In reply to Evgeny Karpov from comment #13) > Could you please confirm that the patch resolves the issue? People like you need to be fired

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #16 from cqwrteur --- This is insane. I am a Microsoft shareholder so technically I am your boss. Why would you ask your boss to waste time for doing your job? Sent from Mail for Windo

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #17 from cqwrteur --- https://github.com/trcrsired/toolchainbuildscripts/blob/main/gccbuild/x86_64-w64-mingw32/x86_64-w64-mingw32.sh Here is the automatic script. Go and test yourself

[Bug tree-optimization/115694] ICE when building scipy with LTO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115694 --- Comment #4 from Sam James --- Reduced. meson-generated_cython_special.c.i: ``` _Complex a; void special_cairye(); void b() { special_cairye(a); } ``` special_wrappers.cpp.ii: ``` typedef struct { double a[2]; } b; extern "C" void special

[Bug tree-optimization/115694] ICE when building scipy with LTO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115694 --- Comment #5 from Sam James --- Bit smaller: ``` gcc -O1 -flto -c meson-generated_cython_special.c.i -o meson-generated_cython_special.c.o g++ -O1 -flto -fvisibility=hidden -shared special_wrappers.cpp.ii meson-generated_cython_special.c.o -o

[Bug target/115688] [15 regression] ICE on simple test case from r15-703-gb390b011569635

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115688 --- Comment #2 from Kewen Lin --- The assertion does expose an inconsistent combination !TARGET_ALTIVEC but TARGET_VSX wiht 32-bit target attribute -mvsx. There is one special handling for altivec_abi: /* Disable VSX and Altivec silently if

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #18 from Sergei Trofimovich --- (In reply to Evgeny Karpov from comment #13) > Could you please confirm that the patch resolves the issue? The change fixes --target=i686-w64-mingw32 for me. Thank you!

[Bug fortran/104130] [12/13 Regression] ICE in gfc_add_class_array_ref, at fortran/class.c:274 since r12-4467-g64f9623765da3306

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104130 Andre Vehreschild changed: What|Removed |Added CC||vehre at gcc dot gnu.org --- Commen

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #19 from cqwrteur --- Then just merge it into the main repo if it works. I have no time for testing because my machine is super slow and I have no idea what’s going on. BTW, it is still insane Microsoft employee would ask Microsoft

[Bug tree-optimization/115694] ICE when building scipy with LTO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115694 --- Comment #6 from Sam James --- Bit more. meson-generated_cython_special.c.i: ``` _Complex a; void special_cairye(); void b() { special_cairye(a); } ``` special_wrappers.cpp.ii: ``` typedef struct { double a[2]; } b; extern "C" void specia

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #20 from Jonathan Wakely --- Your attitude and behaviour is not acceptable, as you've been told many times before. You will be banned if you continue. https://gcc.gnu.org/conduct.html

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #21 from cqwrteur --- First, the bug is not caused by me and I am just reporting the issue here. Why should I waste my time to test for him? Second, I am tired of building compilers again and again just to fix a regression every day

[Bug bootstrap/115696] New: [15 regression] ICE on invalid repeated mixed declarations (tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in comptypes_verify, at c/c-typeck.cc:1178)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115696 Bug ID: 115696 Summary: [15 regression] ICE on invalid repeated mixed declarations (tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in comptypes_verify, at

[Bug fortran/104130] [12/13 Regression] ICE in gfc_add_class_array_ref, at fortran/class.c:274 since r12-4467-g64f9623765da3306

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104130 anlauf at gcc dot gnu.org changed: What|Removed |Added Keywords|ice-on-valid-code |ice-on-invalid-code --- Comm

[Bug tree-optimization/115693] 8 std::byte std::array comparison potential missed optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115693 --- Comment #2 from Jonathan Wakely --- (In reply to Xi Ruoyao from comment #1) > So it makes more sense to fix this in the optimization passes, instead of > ad-hoc hack in libstdc++. Yes, I agree, although we already have the hack in libstdc++

[Bug fortran/115689] Missed deallocation before exit

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115689 --- Comment #5 from anlauf at gcc dot gnu.org --- (In reply to Jerry DeLisle from comment #4) > (In reply to kargls from comment #3) > > The code you posted is standard conforming, and when > > compiled, executes as expected. > > > > My point is

[Bug tree-optimization/115694] [13/14/15 regression] ICE when building scipy with LTO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115694 --- Comment #7 from Sam James --- Standalone, no LTO: ``` _Complex a; void c(); void d() { c(a); } typedef struct { double a[2]; } b; void e(); void c(b f) { e(f); } ``` ``` $ gcc -c special_wrappers.c.i -O1 during GIMPLE pass: forwprop speci

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 Jonathan Wakely changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigne

[Bug tree-optimization/115697] New: Miscompilation with -fgraphite-identity at -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115697 Bug ID: 115697 Summary: Miscompilation with -fgraphite-identity at -O2 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 --- Comment #1 from Jonathan Wakely --- We can use is_same_v<_ValueType1, byte> instead, which is more efficient to compile than instantiating __is_byte unconditionally.

[Bug libstdc++/114149] lexicographical_compare should use memcmp for C++20 contiguous iterators as well as pointers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114149 --- Comment #1 from Jonathan Wakely --- We would need something like this to ensure we don't use memcmp for insane iterators that use exceptions for flow control to exit algorithms early: // N.B. this is not the same as nothrow-forward-iterat

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 Jan Schultke changed: What|Removed |Added CC||janschultke at googlemail dot com --- C

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 --- Comment #3 from Jonathan Wakely --- #include enum E { e }; bool operator==(E, E) { return false; } int main() { E e[1]; return std::equal(e, e+1, e); }

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 --- Comment #4 from Jonathan Wakely --- It's valid for std::byte because we know what equality means for std::byte. You could maaybe do something like: template concept is_sane_enum = is_enum_v && (!requires { &operator==(E,E); }); but I'

[Bug driver/115698] New: @file invalidates -B in g++ command line

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115698 Bug ID: 115698 Summary: @file invalidates -B in g++ command line Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: drive

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 --- Comment #5 from Jan Schultke --- &operator==(E,E); is not a valid expression, but I understand what you're trying to do there. Perhaps you can test by converting to a function pointer bool(*)(E,E). It would surely miss cases like an operato

[Bug tree-optimization/115693] 8 std::byte std::array comparison potential missed optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115693 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Blocks|

[Bug target/115640] [15 Regression] GCN: FAIL: gfortran.dg/vect/pr115528.f -O execution test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115640 --- Comment #17 from GCC Commits --- The master branch has been updated by Andrew Stubbs : https://gcc.gnu.org/g:ef0b30212f7756db15d7507bfd871bf377d7d648 commit r15-1705-gef0b30212f7756db15d7507bfd871bf377d7d648 Author: Andrew Stubbs Date:

[Bug c/115696] [15 regression] ICE on invalid repeated mixed declarations (tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in comptypes_verify, at c/c-typeck.cc:1178)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115696 Richard Biener changed: What|Removed |Added Version|unknown |15.0 Target Milestone|---

[Bug target/115640] [15 Regression] GCN: FAIL: gfortran.dg/vect/pr115528.f -O execution test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115640 --- Comment #18 from Andrew Stubbs --- That should fix the broken validation check. All V32 permutations should work now on RDNA GPUs, I think. V16 and smaller were already working fine.

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 --- Comment #6 from Jonathan Wakely --- (In reply to Jan Schultke from comment #5) > It would surely miss cases like an operator== with an always-defaulted third > parameter, That's not valid, operator== must have two parameters. > or one wher

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 --- Comment #7 from Jonathan Wakely --- A better version of the concept sketched above: template concept is_sane_enum = std::is_enum_v && (!requires { [] U>(U (*)(T, T)){}(&operator==); });

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 --- Comment #8 from Jan Schultke --- It is a tiny bit pessimistic if it uses std::convertible_to instead of std::__boolean_testable or what it was called. I cannot come up with an example that produces a false positive though (which is crucial

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 --- Comment #9 from Jonathan Wakely --- I'm still not willing to use that though.

[Bug libstdc++/107367] All standard library algorithms should optimize to pointers internally when they are contiguous iterators after C++20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107367 --- Comment #5 from Jonathan Wakely --- This optimization isn't valid if any iterator operations can throw, because such an exception should terminate the loop early. Performing the algo on raw pointers would alter the behaviour.

[Bug target/115640] [15 Regression] GCN: FAIL: gfortran.dg/vect/pr115528.f -O execution test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115640 --- Comment #19 from GCC Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:0192341a07b8ea30f631cf4afdc6fcf3fa7ce838 commit r15-1706-g0192341a07b8ea30f631cf4afdc6fcf3fa7ce838 Author: Richard Biener Date:

[Bug target/115640] [15 Regression] GCN: FAIL: gfortran.dg/vect/pr115528.f -O execution test

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115640 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/115697] [11/12/13/14/15 Regression] Miscompilation with -fgraphite-identity at -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115697 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org Known to fai

[Bug c++/94058] defaulted three way comparison operator defined as deleted when a member is a small bitfield of long type.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94058 Mital Ashok changed: What|Removed |Added CC||mital at mitalashok dot co.uk --- Comment

[Bug fortran/115689] Missed deallocation before exit

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115689 Mikael Morin changed: What|Removed |Added CC||mikael at gcc dot gnu.org --- Comment #6

[Bug c++/115699] New: Anonymous structs should compare member-wise with C++20 defaulted operator==

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115699 Bug ID: 115699 Summary: Anonymous structs should compare member-wise with C++20 defaulted operator== Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: n

[Bug tree-optimization/55001] Handle VEC_COND_EXPR better in tree-vect-generic.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55001 --- Comment #8 from Richard Biener --- Testcase: typedef int v32si __attribute__((vector_size(128))); void foo (v32si *a, v32si *b, v32si *c) { *c = *a < *b ? (v32si){-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1, -1,-1,-1,-1,-1

[Bug target/114137] ICE when building lua-5.4.6 with -fharden-control-flow-redundancy on x86 (error: invalid rtl sharing found in the insn)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114137 --- Comment #7 from Sam James --- Hi Alexandre, not forgot about this (and thanks for the kind help). I'll let you know when got more information.

[Bug target/114137] ICE when building lua-5.4.6 with -fharden-control-flow-redundancy on x86 (error: invalid rtl sharing found in the insn)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114137 Sam James changed: What|Removed |Added Last reconfirmed||2024-06-28 Status|UNCONFIRMED

[Bug tree-optimization/55001] Handle VEC_COND_EXPR better in tree-vect-generic.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55001 --- Comment #9 from Richard Biener --- Note it's going to be _way_ easier to tackle when we got rid of vcond{,u,eq} since then the compares and the condition can be lowered separately.

[Bug target/115661] [15 Regression] wrong code at -O{2,3} on x86_64-linux-gnu since r15-1599-g63512c72df09b4

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115661 --- Comment #9 from GCC Commits --- The master branch has been updated by Christophe Lyon : https://gcc.gnu.org/g:c4b7b62bfa10816c1e08f0f9597d857f11379688 commit r15-1708-gc4b7b62bfa10816c1e08f0f9597d857f11379688 Author: Evgeny Karpov Date:

[Bug bootstrap/115635] [15 regression] Bootstrap fails with failed self-test with the rust fe (diagnostic-path.cc:1153: test_empty_path: FAIL: ASSERT_FALSE ((path.interprocedural_p ()))) since r15-159

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115635 --- Comment #14 from GCC Commits --- The master branch has been updated by Christophe Lyon : https://gcc.gnu.org/g:c4b7b62bfa10816c1e08f0f9597d857f11379688 commit r15-1708-gc4b7b62bfa10816c1e08f0f9597d857f11379688 Author: Evgeny Karpov Date:

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 --- Comment #22 from GCC Commits --- The master branch has been updated by Christophe Lyon : https://gcc.gnu.org/g:c4b7b62bfa10816c1e08f0f9597d857f11379688 commit r15-1708-gc4b7b62bfa10816c1e08f0f9597d857f11379688 Author: Evgeny Karpov Date:

[Bug target/115661] [15 Regression] wrong code at -O{2,3} on x86_64-linux-gnu since r15-1599-g63512c72df09b4

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115661 Christophe Lyon changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug bootstrap/115635] [15 regression] Bootstrap fails with failed self-test with the rust fe (diagnostic-path.cc:1153: test_empty_path: FAIL: ASSERT_FALSE ((path.interprocedural_p ()))) since r15-159

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115635 Bug 115635 depends on bug 115661, which changed state. Bug 115661 Summary: [15 Regression] wrong code at -O{2,3} on x86_64-linux-gnu since r15-1599-g63512c72df09b4 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115661 What|Removed

[Bug tree-optimization/115652] [15 Regression] GCN: FAIL: gcc.dg/vect/pr70138-{1,2}.c (internal compiler error: verify_ssa failed)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115652 --- Comment #9 from GCC Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:ff6e8b7f09712bd7ddfcd2830b286421f23abef9 commit r15-1709-gff6e8b7f09712bd7ddfcd2830b286421f23abef9 Author: Richard Biener Date:

[Bug tree-optimization/115652] [15 Regression] GCN: FAIL: gcc.dg/vect/pr70138-{1,2}.c (internal compiler error: verify_ssa failed)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115652 Richard Biener changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

[Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643 Christophe Lyon changed: What|Removed |Added Resolution|--- |FIXED CC|

[Bug bootstrap/115635] [15 regression] Bootstrap fails with failed self-test with the rust fe (diagnostic-path.cc:1153: test_empty_path: FAIL: ASSERT_FALSE ((path.interprocedural_p ()))) since r15-159

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115635 Christophe Lyon changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug c++/94058] defaulted three way comparison operator defined as deleted when a member is a small bitfield of long type.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94058 Marek Polacek changed: What|Removed |Added Last reconfirmed||2024-06-28 Ever confirmed|0

[Bug libstdc++/115585] [12/13/14/15 Regression] --disable-libstdcxx-verbose causes undefined symbol: _ZSt21__glibcxx_assert_failPKciS0_S0_, version GLIBCXX_3.4.30

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115585 Jonathan Wakely changed: What|Removed |Added Summary|--disable-libstdcxx-verbose |[12/13/14/15 Regression]

[Bug fortran/115700] New: [10/11/12/13/14 regression] Bogus warning for associate with assumed-length character array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115700 Bug ID: 115700 Summary: [10/11/12/13/14 regression] Bogus warning for associate with assumed-length character array Product: gcc Version: 10.4.0 Status: UNCONFIRMED

[Bug target/115688] [15 regression] ICE on simple test case from r15-703-gb390b011569635

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115688 --- Comment #3 from Segher Boessenkool --- Something like that. But why would we want to disable generation of VSX or VMX insns at all? This is similar to disabling generation of popcntd insns if you do not like those! Having generation of V*X

[Bug target/115673] [15 regression] gcc.target/i386/force-indirect-call-2.c test failure

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115673 --- Comment #5 from Sam James --- Still fails with the GOT alias set fix on trunk.

[Bug target/115688] [15 regression] ICE on simple test case from r15-703-gb390b011569635

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115688 --- Comment #4 from Peter Bergner --- (In reply to Kewen Lin from comment #2) > // 32 bit has altivec_abi unset, so that's why it doesn't ICE at -m64. Ah yes, that does explain the difference between 32-bit and 64-bit! ...and that means it ICEs

[Bug libstdc++/107367] All standard library algorithms should optimize to pointers internally when they are contiguous iterators after C++20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107367 --- Comment #6 from cqwrteur --- Your argument is not correct when you can just detect all the iterator methods are noexcept. Plus, the standard does not need you to handle exceptions if iterator throw it but to terminate. Btw what is the point

[Bug libstdc++/107367] All standard library algorithms should optimize to pointers internally when they are contiguous iterators after C++20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107367 --- Comment #7 from cqwrteur --- I see similar side effects like what if someone adds a print statement in the operator++ or operator * in a contiguous iterator and etc. If I am not allowed to use std::to_address, what’s the point?

[Bug target/115688] [15 regression] ICE on simple test case from r15-703-gb390b011569635

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115688 --- Comment #5 from Segher Boessenkool --- (In reply to Peter Bergner from comment #4) > bergner@ltcden2-lp1:ICE$ gcc -S -m64 -O2 -mcpu=power5 -mabi=no-altivec bug.c > bug.c:3:1: internal compiler error: in rs6000_option_override_internal, at >

[Bug c++/94058] defaulted three way comparison operator defined as deleted when a member is a small bitfield of long type.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94058 --- Comment #4 from Marek Polacek --- This may implement that DR: --- a/gcc/cp/typeck2.cc +++ b/gcc/cp/typeck2.cc @@ -1012,6 +1012,14 @@ check_narrowing (tree type, tree init, tsubst_flags_t complain, if (TREE_CODE (ftype) == ENUMERAL_TYP

[Bug c++/94058] defaulted three way comparison operator defined as deleted when a member is a small bitfield of long type.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94058 --- Comment #5 from Mital Ashok --- Proposed patch doesn't seem to work with bool bit-fields (with width not-1): ``` struct X { bool bf : 8; } x; signed char x_not_narrow{ x.bf }; ``` Currently: Not narrowing With patch: ``` test.cpp:4:29: w

[Bug c++/69560] x86_64: alignof(uint64_t) produces incorrect results with -m32

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69560 --- Comment #25 from GCC Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:ac8c61b62e71ffdcaebfd4cfc03f58fe542855dd commit r15-1713-gac8c61b62e71ffdcaebfd4cfc03f58fe542855dd Author: Jonathan Wakely Date:

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 --- Comment #10 from GCC Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:fab60eaa94b50b1eea84f0d001004c851d4c781b commit r15-1715-gfab60eaa94b50b1eea84f0d001004c851d4c781b Author: Jonathan Wakely Date

[Bug libstdc++/115585] [12/13/14/15 Regression] --disable-libstdcxx-verbose causes undefined symbol: _ZSt21__glibcxx_assert_failPKciS0_S0_, version GLIBCXX_3.4.30

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115585 --- Comment #12 from GCC Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:52370c839edd04df86d3ff2b71fcdca0c7376a7f commit r15-1716-g52370c839edd04df86d3ff2b71fcdca0c7376a7f Author: Jonathan Wakely Date

[Bug libstdc++/104395] ext/bitmap_allocator.h is not C++98 friendly when using with -faligned-new

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104395 --- Comment #10 from GCC Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:03d3aeb0e0fa7dec9bd702cabf57ef73cdc32704 commit r15-1714-g03d3aeb0e0fa7dec9bd702cabf57ef73cdc32704 Author: Jonathan Wakely Date

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Target Milestone|---

[Bug c++/94058] defaulted three way comparison operator defined as deleted when a member is a small bitfield of long type.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94058 --- Comment #6 from Marek Polacek --- Right, I need to handle "the source is a bit-field whose width w is less than that of its type" as well; is_bitfield_expr_with_lowered_type doesn't do that. Thanks!

[Bug ipa/115701] New: wrong code at -O1 and above with "-fipa-pta" on x86_64-linux-gnu

/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 15.0.0 20240628 (experimental) (GCC) [538] % [538] % gcctk -O1 small.c; ./a.out [539] % [539] % gcctk -O1

[Bug libstdc++/115668] Cannot format chrono::duration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115668 --- Comment #3 from GCC Commits --- The releases/gcc-14 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:d5e352addf4c17d28bcada42409881089c5d8088 commit r14-10356-gd5e352addf4c17d28bcada42409881089c5d8088 Author: Jonathan Wak

[Bug libstdc++/115668] Cannot format chrono::duration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115668 --- Comment #4 from GCC Commits --- The releases/gcc-13 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:4b64a1051a927a65a9acefbbb5714a8118c320bc commit r13-8877-g4b64a1051a927a65a9acefbbb5714a8118c320bc Author: Jonathan Wake

[Bug libstdc++/115668] Cannot format chrono::duration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115668 Jonathan Wakely changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c++/115658] char16_t and char32_t aliasing is conserative

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115658 --- Comment #3 from Tom Honermann --- In retrospect, I think I misunderstood Andrew's motivation for filing this issue. There is a difference of behavior between gcc and clang with regard to aliasing of `char16_t` and `char32_t` with respect to

[Bug fortran/114019] allocation with source of deferred character length entity

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114019 anlauf at gcc dot gnu.org changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot gnu

[Bug ipa/115701] [11/12/13/14/15 Regression] wrong code at -O1 and above with "-fipa-pta" on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115701 Andrew Pinski changed: What|Removed |Added Summary|wrong code at -O1 and above |[11/12/13/14/15 Regression]

[Bug c/115702] New: Incorrect stringop-overflow warning with -O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115702 Bug ID: 115702 Summary: Incorrect stringop-overflow warning with -O3 Product: gcc Version: 14.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug tree-optimization/115274] Bogus -Wstringop-overread in SQLite source code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115274 Andrew Pinski changed: What|Removed |Added CC||christian at zeek dot org --- Comment #

[Bug tree-optimization/115702] Incorrect stringop-overflow warning with -O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115702 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/88443] [meta-bug] bogus/missing -Wstringop-overflow warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443 Bug 88443 depends on bug 115702, which changed state. Bug 115702 Summary: Incorrect stringop-overflow warning with -O3 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115702 What|Removed |Added

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 --- Comment #12 from Jan Schultke --- On a language evolution note, https://wg21.link/P2825 would let you detect whether an equality comparison for enumerations is overloaded by checking whether > declcall(E{} == E{}) ... is well-formed. If th

[Bug driver/115698] @file invalidates -B in g++ command line

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115698 --- Comment #1 from Andrew Pinski --- So I looked into the driver code and '@' handling is early on and just expands into the new arguments.

[Bug driver/115698] @file invalidates -B in g++ command line

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115698 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2024-06-28 Ever confirmed|0

[Bug tree-optimization/115697] [11/12/13/14/15 Regression] Miscompilation with -fgraphite-identity at -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115697 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |11.5

[Bug tree-optimization/35356] Missing Index splitting support in gcc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35356 Andrew Pinski changed: What|Removed |Added Blocks||26163 CC|

[Bug tree-optimization/115274] Bogus -Wstringop-overread in SQLite source code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115274 D. Richard Hipp changed: What|Removed |Added CC||drh at sqlite dot org --- Comment #6

[Bug tree-optimization/115694] [13/14/15 regression] ICE in forwprop (useless_type_conversion_p) when building scipy with LTO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115694 Andrew Pinski changed: What|Removed |Added Known to work||12.3.0 Known to fail|

[Bug tree-optimization/115694] [13/14/15 regression] ICE in forwprop (useless_type_conversion_p) when building scipy with LTO

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115694 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug c++/115358] [13/14/15 Regression] template argument deduction/substitution failed in generic lambda function use of static constexpr array type whos initializer defines the size since r13-2540

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115358 --- Comment #9 from GCC Commits --- The releases/gcc-14 branch has been updated by Patrick Palka : https://gcc.gnu.org/g:33a9c4dd5fcac7e3f5d835b35fe787126339dd2b commit r14-10357-g33a9c4dd5fcac7e3f5d835b35fe787126339dd2b Author: Patrick Palka

[Bug c++/115504] [14/15 Regression] Wrong decltype result for a captured reference inside lambda since r14-5330

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115504 --- Comment #4 from GCC Commits --- The releases/gcc-14 branch has been updated by Patrick Palka : https://gcc.gnu.org/g:e6b115be1c392de415925282a38f28cd78cb6c35 commit r14-10359-ge6b115be1c392de415925282a38f28cd78cb6c35 Author: Patrick Palka

[Bug c++/115198] Class template argument deduction fails for copy ctor when used with an alias template if the aliased class template has explicitly defaulted copy ctor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115198 --- Comment #6 from GCC Commits --- The releases/gcc-14 branch has been updated by Patrick Palka : https://gcc.gnu.org/g:a00a8d46ea6ff7130e2493e7bd9824e28e2509b7 commit r14-10358-ga00a8d46ea6ff7130e2493e7bd9824e28e2509b7 Author: Patrick Palka

[Bug c++/115358] [13 Regression] template argument deduction/substitution failed in generic lambda function use of static constexpr array type whos initializer defines the size since r13-2540

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115358 Patrick Palka changed: What|Removed |Added Summary|[13/14/15 Regression] |[13 Regression] template

  1   2   >