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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115694 Richard Biener changed: What|Removed |Added Priority|P3 |P2

[Bug target/115683] [15 Regression] SSE2 regressions after obselete of vcond{,u,eq}.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115683 Richard Biener changed: What|Removed |Added Last reconfirmed||2024-07-01 Status|UNCONFIR

[Bug c++/115715] gcc seems to incorrectly accept illegal constexpr constructor in virtual inheritance and static template class member

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115715 Xi Ruoyao changed: What|Removed |Added Keywords|accepts-invalid |diagnostic Severity|normal

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #12 from Andrew Pinski --- (In reply to Jason Liam from comment #11) > Just like in the other example(https://godbolt.org/z/GbTcvT9z8), the > [expr.prim.lambda.closure/2] only implies that the closure-types will be > declared in the

[Bug c++/115715] gcc seems to incorrectly accept illegal constexpr constructor in virtual inheritance and static template class member

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115715 --- Comment #4 from Xi Ruoyao --- (In reply to Andrew Pinski from comment #3) > Confirmed. This is a QoI issue though. We should do more rejections on > non-dependent types inside templates. Should we open an enhancement like "reject templates

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #11 from Jason Liam --- Just like in the other example(https://godbolt.org/z/GbTcvT9z8), the [expr.prim.lambda.closure/2] only implies that the closure-types will be declared in the global scope. Nothing else. The uniqueness is dete

[Bug target/115517] Fix x86 regressions after dropping uses of vcond{,u,eq}_optab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 --- Comment #16 from Richard Biener --- (In reply to Hongtao Liu from comment #14) > regressions above SSE4.1 are fxed in GCC15, SSE2 regressions are tracked in > PR115683 Thanks a lot for the effort!

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #10 from Jason Liam --- (In reply to Andrew Pinski from comment #7) > The question is does the lambda type in a default argument gets defined once > even if it is evaluated twice. I think so based on > expr.prim.lambda.closure/2 . I

[Bug tree-optimization/115710] [11/12/13/14/15 Regression] complex abs does not vectorise

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115710 --- Comment #11 from rguenther at suse dot de --- On Sun, 30 Jun 2024, pinskia at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115710 > > --- Comment #8 from Andrew Pinski --- > I wonder if we could also add: > +/* ca

[Bug rtl-optimization/115717] volatile store hampering unrelated optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115717 Richard Biener changed: What|Removed |Added Last reconfirmed||2024-07-01 Ever confirmed|0

[Bug target/115723] SPEC CPU2017 521/621 build error with -Ofast and AVX512 enabled(-ftree-vectorize?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115723 --- Comment #7 from Andrew Pinski --- The assert that is being hitting: bool cond_fn_p = code.is_internal_fn () && conditional_internal_fn_code (internal_fn (code)) != ERROR_MARK; if (cond_fn_p) { gcc_assert (code == IFN_COND_A

[Bug target/115723] SPEC CPU2017 521/621 build error with -Ofast and AVX512 enabled(-ftree-vectorize?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115723 --- Comment #6 from Andrew Pinski --- /home/edison/gcc14/libexec/gcc/x86_64-pc-linux-gnu/14.1.0/f951 module_sf_bep.fppized.f90 -I . -I ./netcdf/include -I ./inc -quiet -dumpbase module_sf_bep.fppized.f90 -dumpbase-ext .f90 -m64 -march=x86-64-v4

[Bug target/115723] SPEC CPU2017 521/621 build error with -Ofast and AVX512 enabled(-ftree-vectorize?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115723 --- Comment #5 from edison --- gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/home/edison/gcc14/libexec/gcc/x86_64-pc-linux-gnu/14.1.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../configure --prefix=/home/ediso

[Bug target/115723] SPEC CPU2017 521/621 build error with -Ofast and AVX512 enabled(-ftree-vectorize?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115723 --- Comment #4 from edison --- (In reply to Andrew Pinski from comment #2) > Also what version of binutils are you using? If there is an assembly error. ld -v GNU ld (GNU Binutils for Ubuntu) 2.42

[Bug target/115723] SPEC CPU2017 521/621 build error with -Ofast and AVX512 enabled(-ftree-vectorize?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115723 --- Comment #3 from edison --- Created attachment 58547 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58547&action=edit the output file which build with -march=x86-64-v4 -v-Ofast

[Bug middle-end/115719] __builtin_memcmp missed if it compare length of 3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115719 Richard Biener changed: What|Removed |Added Version|unknown |15.0 Ever confirmed|0

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #9 from Andrew Pinski --- (In reply to Jason Liam from comment #8) > > Which means the closure type is in the global scope here for this TU. > > I did read that before posting actually. But even if they're in the global > scope in s

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115694 --- Comment #13 from GCC Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:543a5b9da964f821b9e723ed9c93d6cdca464d47 commit r15-1743-g543a5b9da964f821b9e723ed9c93d6cdca464d47 Author: Richard Biener Date:

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #8 from Jason Liam --- > Which means the closure type is in the global scope here for this TU. I did read that before posting actually. But even if they're in the global scope in same TUs they should still produce unique/distinct c

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #7 from Andrew Pinski --- (In reply to Jason Liam from comment #6) > https://stackoverflow.com/questions/50417782/is-it-safe-to-assume-that- > identical-lambda-expressions-have-different-types The question is does the lambda type in

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #6 from Jason Liam --- https://stackoverflow.com/questions/50417782/is-it-safe-to-assume-that-identical-lambda-expressions-have-different-types

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #5 from Andrew Pinski --- You missed this part: The closure type is declared in the smallest block scope, class scope, or namespace scope that contains the corresponding lambda-expression. from expr.prim.lambda.closure/2 Which mean

[Bug analyzer/115724] New: analyzer does not recognise non-returning error()

─>(4) ...to here 'list_create': event 5 25 | result->destroy = destroy; | ^ | | | (5) ⚠️ dereference of NULL 'result' ------ Using built-in

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #4 from Andrew Pinski --- (In reply to Jason Liam from comment #3) > [expr.prim.lambda.closure] states: > > > The type of a lambda-expression (which is also the type of the closure > > object) is a unique, unnamed non-union class t

[Bug target/114189] Target implements obsolete vcond{,u,eq} expanders

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114189 Bug 114189 depends on bug 115517, which changed state. Bug 115517 Summary: Fix x86 regressions after dropping uses of vcond{,u,eq}_optab https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 What|Removed |Added

[Bug target/115517] Fix x86 regressions after dropping uses of vcond{,u,eq}_optab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 Hongtao Liu changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug target/115517] Fix x86 regressions after dropping uses of vcond{,u,eq}_optab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 --- Comment #14 from Hongtao Liu --- regressions above SSE4.1 are fxed in GCC15, SSE2 regressions are tracked in PR115683

[Bug target/115517] Fix x86 regressions after dropping uses of vcond{,u,eq}_optab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 --- Comment #13 from GCC Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:55f80c690c5fa59836646565a9dee2a3f68374a0 commit r15-1742-g55f80c690c5fa59836646565a9dee2a3f68374a0 Author: liuhongt Date: Mon Jun

[Bug target/115517] Fix x86 regressions after dropping uses of vcond{,u,eq}_optab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 --- Comment #12 from GCC Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:2ccdd0f22312a14ac64bf944fdc4f8e7532eb0eb commit r15-1741-g2ccdd0f22312a14ac64bf944fdc4f8e7532eb0eb Author: liuhongt Date: Thu Jun

[Bug target/115517] Fix x86 regressions after dropping uses of vcond{,u,eq}_optab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 --- Comment #11 from GCC Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:e94e6ee495d95f29355bbc017214228a5e367638 commit r15-1740-ge94e6ee495d95f29355bbc017214228a5e367638 Author: liuhongt Date: Wed Jun

[Bug target/115517] Fix x86 regressions after dropping uses of vcond{,u,eq}_optab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 --- Comment #10 from GCC Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:3cb204046c0db899750aee9480af4f1953a40ac3 commit r15-1739-g3cb204046c0db899750aee9480af4f1953a40ac3 Author: liuhongt Date: Wed Jun

[Bug target/115517] Fix x86 regressions after dropping uses of vcond{,u,eq}_optab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 --- Comment #9 from GCC Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:09737d9605521df9232d9990006c44955064f44e commit r15-1738-g09737d9605521df9232d9990006c44955064f44e Author: liuhongt Date: Tue Jun

[Bug target/115517] Fix x86 regressions after dropping uses of vcond{,u,eq}_optab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 --- Comment #8 from GCC Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:b06a108f0fbffe12493b527224f6e4131a72beac commit r15-1737-gb06a108f0fbffe12493b527224f6e4131a72beac Author: liuhongt Date: Tue Jun

[Bug target/115517] Fix x86 regressions after dropping uses of vcond{,u,eq}_optab

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115517 --- Comment #7 from GCC Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:2e2dfa0095c3326a0a5fc2ff175918b42eeb044f commit r15-1736-g2e2dfa0095c3326a0a5fc2ff175918b42eeb044f Author: liuhongt Date: Mon Jun

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #3 from Jason Liam --- [expr.prim.lambda.closure] states: > The type of a lambda-expression (which is also the type of the closure > object) is a unique, unnamed non-union class type, called the closure type, > ... --

[Bug target/115723] SPEC CPU2017 521/621 build error with -Ofast and AVX512 enabled.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115723 Andrew Pinski changed: What|Removed |Added Target||x86_64-linux-gnu Component|tre

[Bug tree-optimization/115723] SPEC CPU2017 521/621 build error with -Ofast and AVX512 enabled.

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

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #2 from Andrew Pinski --- > also the type of a lambda expression is unique each time I don't see anywhere it should be unique each time unless I am missing something.

[Bug c++/115722] GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 --- Comment #1 from Andrew Pinski --- Hmm, GCC, clang and MSVC (and from the looks of it, EDG via ICC) too all have the same behavior.

[Bug fortran/115723] New: SPEC CPU2017 521/621 build error with -Ofast and AVX512 enabled.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115723 Bug ID: 115723 Summary: SPEC CPU2017 521/621 build error with -Ofast and AVX512 enabled. Product: gcc Version: 14.1.0 Status: UNCONFIRMED Severity: normal

[Bug c++/115722] New: GCC uses old closure type when using as default argument instead of using new closure type each time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115722 Bug ID: 115722 Summary: GCC uses old closure type when using as default argument instead of using new closure type each time Product: gcc Version: 15.0 Status: UNCONFIRM

[Bug c++/115720] module symbol collision

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115720 --- Comment #1 from cqwrteur --- https://www.reddit.com/r/cpp/comments/1dqhlh2/c_modules_discussion_ask_questions_and_share_your/ import std; #include // or any other standard library header Looks like defects in the C++ standard that does no

[Bug target/115610] -flate-combine disabled by default for x86 port

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115610 Hongtao Liu changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug target/115610] -flate-combine disabled by default for x86 port

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115610 --- Comment #3 from GCC Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:8e1fa107a63b2e160b6bf69de4fe163dd3cebd80 commit r15-1734-g8e1fa107a63b2e160b6bf69de4fe163dd3cebd80 Author: liuhongt Date: Wed Jun

[Bug target/115610] -flate-combine disabled by default for x86 port

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115610 --- Comment #2 from GCC Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:5e1a9f4ccff390ae79a9b9d0d39b325f2b4ea925 commit r15-1733-g5e1a9f4ccff390ae79a9b9d0d39b325f2b4ea925 Author: liuhongt Date: Wed Jun

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115693 Hongtao Liu changed: What|Removed |Added CC||liuhongt at gcc dot gnu.org --- Comment #

[Bug tree-optimization/115710] [11/12/13/14/15 Regression] complex abs does not vectorise

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115710 --- Comment #10 from Andrew Pinski --- (In reply to Andrew Pinski from comment #9) > (In reply to Andrew Pinski from comment #8) > > I wonder if we could also add: > > +/* cabs(x+0i) or cabs(0+xi) -> abs(x). */ > > +(simplify > > + (CABS (compl

[Bug tree-optimization/115721] expand_complex_comparison has handling of GIMPLE_RETURN but a comparison can't be in a return

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

[Bug tree-optimization/115721] New: expand_complex_comparison has handling of GIMPLE_RETURN but a comparison can't be in a return

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115721 Bug ID: 115721 Summary: expand_complex_comparison has handling of GIMPLE_RETURN but a comparison can't be in a return Product: gcc Version: 15.0 Status: UNCONFIRMED

[Bug tree-optimization/115710] [11/12/13/14/15 Regression] complex abs does not vectorise

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115710 --- Comment #9 from Andrew Pinski --- (In reply to Andrew Pinski from comment #8) > I wonder if we could also add: > +/* cabs(x+0i) or cabs(0+xi) -> abs(x). */ > +(simplify > + (CABS (complex:c @0 real_zerop@1)) > + (abs @0)) > > > + /* cabs(

[Bug c++/115720] New: module symbol collision

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115720 Bug ID: 115720 Summary: module symbol collision Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assigne

[Bug middle-end/115719] __builtin_memcmp missed if it compare length of 3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115719 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement Target|

[Bug c/115719] New: __builtin_memcmp missed if it compare length of 3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115719 Bug ID: 115719 Summary: __builtin_memcmp missed if it compare length of 3 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Compon

[Bug libstdc++/100663] dietlibc build fail 'FP_NAN' was not declared in this scope

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100663 Jonathan Wakely changed: What|Removed |Added Resolution|--- |INVALID Status|WAITING

[Bug libstdc++/100663] dietlibc build fail 'FP_NAN' was not declared in this scope

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100663 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2024-06-30 Status|UNCONFI

[Bug tree-optimization/115710] [11/12/13/14/15 Regression] complex abs does not vectorise

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115710 --- Comment #8 from Andrew Pinski --- I wonder if we could also add: +/* cabs(x+0i) or cabs(0+xi) -> abs(x). */ +(simplify + (CABS (complex:c @0 real_zerop@1)) + (abs @0)) + /* cabs(x+xi) -> fabs(x)*sqrt(2). */ + (simplify + (CABS (complex

[Bug tree-optimization/115710] [11/12/13/14/15 Regression] complex abs does not vectorise

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115710 --- Comment #7 from Andrew Pinski --- Created attachment 58544 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58544&action=edit Patch which I am testing I will add a few testcases too.

[Bug fortran/115711] Fortran: extra malloc and copy with transfer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115711 anlauf at gcc dot gnu.org changed: What|Removed |Added CC||anlauf at gcc dot gnu.org --

[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 Resolution|--- |FIXED Status|NEW

[Bug fortran/55978] class_optional_2.f90 -Os fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55978 --- Comment #35 from GCC Commits --- The releases/gcc-14 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:9f147487de660f026e2fb1281e1a1800f58b3bdd commit r14-10363-g9f147487de660f026e2fb1281e1a1800f58b3bdd Author: Harald Anlauf

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114019 --- Comment #5 from GCC Commits --- The releases/gcc-14 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:603b344c07aa55f8292446e8fd28f5da9a983a21 commit r14-10364-g603b344c07aa55f8292446e8fd28f5da9a983a21 Author: Harald Anlauf

[Bug fortran/115390] Bogus -Wuninitialized warning when using CHARACTER(*) argument in BIND(C) function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115390 --- Comment #7 from GCC Commits --- The releases/gcc-14 branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:b31e1900fa0cffabb0702962d01ba3fe917fdf69 commit r14-10362-gb31e1900fa0cffabb0702962d01ba3fe917fdf69 Author: Harald Anlauf

[Bug tree-optimization/115710] [11/12/13/14/15 Regression] complex abs does not vectorise

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115710 Andrew Pinski changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug c++/115715] gcc seems to incorrectly accept illegal constexpr constructor in virtual inheritance and static template class member

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115715 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2024-06-30 Status|UNCONFIRM

[Bug tree-optimization/115710] [11/12/13/14/15 Regression] complex abs does not vectorise

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115710 --- Comment #5 from Andrew Pinski --- (In reply to Richard Biener from comment #4) > I wonder if we shouldn't do CABS expansion during complex lowering instead? It would be one less pass around the IR too so it could speed up the compiler sligh

[Bug c++/66564] [11/12/13/14/15 Regression] ICE on explicit instantiation of nested template class

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66564 Andrew Pinski changed: What|Removed |Added Known to fail||4.9.0 Summary|ICE on explicit

[Bug c++/115716] [11/12/13/14/15 regression] internal compiler error: tree check: accessed elt 2 of 'tree_vec' with 1 elts in tsubst, at cp/pt.cc:16364

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115716 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115693 --- Comment #5 from Andrew Pinski --- (In reply to Paulous Haile from comment #4) > Maybe not necessary, just wanted to add a case for the default operator==. I > have noticed it also doesn't seem to coalesce adjacent cmps, which I assume > is p

[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 #7 from Uroš Bizjak --- (In reply to Richard Biener from comment #6) > So it likely expects f1@GOTPCREL(%rip) to be CSEd? > > f2: > .LFB2: > .cfi_startproc > subq$8, %rsp > .cfi_def_cfa_offset 16 >

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115693 --- Comment #4 from Paulous Haile --- Maybe not necessary, just wanted to add a case for the default operator==. I have noticed it also doesn't seem to coalesce adjacent cmps, which I assume is part of the same issue. #include struct Point {

[Bug target/115526] [14/15 regression] invalid assember emitted for alpha, "Error: duplicate !tlsgd!62" since r14-5109-ga291237b628f41

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115526 --- Comment #8 from Uroš Bizjak --- (In reply to Sam James from comment #7) > Uros, is there any chance you'd be so kind to take a look? I'm afraid that this is not some dead-simple issue that I can fix without the access to the alpha machine.

[Bug fortran/102689] Segfault with RESHAPE of CLASS as actual argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102689 Paul Thomas changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org --- Comme

[Bug c++/115718] New: Deficiencies in -Wnrvo

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115718 Bug ID: 115718 Summary: Deficiencies in -Wnrvo Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee

[Bug target/115526] [14/15 regression] invalid assember emitted for alpha, "Error: duplicate !tlsgd!62" since r14-5109-ga291237b628f41

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115526 Sam James changed: What|Removed |Added CC||ubizjak at gmail dot com --- Comment #7 fro

[Bug target/115526] [14/15 regression] invalid assember emitted for alpha, "Error: duplicate !tlsgd!62"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115526 --- Comment #6 from Andreas K. Huettel --- for reference... crossdev ~/bisection/gcc # git bisect log git bisect start # status: waiting for both good and bad commits # good: [c042baa99ef0cb1c1711cd913822ce1e7354f144] testsuite, Darwin: Remove

[Bug libstdc++/107603] checking for ld that supports -Wl,--gc-sections... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. for i686-w64-mingw32 target at canadian compilation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107603 Sam James changed: What|Removed |Added Last reconfirmed||2024-06-30 Ever confirmed|0

[Bug target/115691] [15 Regression] libgomp.c-c++-common/for -2.h:101:33: internal compiler error: in extract_insn, at recog.cc:2816

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115691 --- Comment #4 from GCC Commits --- The master branch has been updated by John David Anglin : https://gcc.gnu.org/g:30ad2fafa9ab2497cc12df62a3240cff6ef25d00 commit r15-1731-g30ad2fafa9ab2497cc12df62a3240cff6ef25d00 Author: John David Anglin D

[Bug c++/115715] gcc seems to incorrectly accept illegal constexpr constructor in virtual inheritance and static template class member

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115715 --- Comment #2 from Xi Ruoyao --- FWIW MSVC gives no diagnostic, and EDG gives a misleading diagnostic: '"", line 11: error: a constexpr variable must have a literal type or a reference type'

[Bug c++/115715] gcc seems to incorrectly accept illegal constexpr constructor in virtual inheritance and static template class member

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115715 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #1 fr

[Bug rtl-optimization/115717] New: volatile store hampering unrelated optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115717 Bug ID: 115717 Summary: volatile store hampering unrelated optimization Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c++/115670] auto placeholder for return type should change the linkage of the function if the type becomes local linkage too

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115670 --- Comment #7 from Federico Kircheis --- I've made a similar report to clang (https://github.com/llvm/llvm-project/issues/97162) and they found another function that could be optimized out ~~~ auto foo7() { return 1; } ~~~ They made me also r

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115694 Richard Biener changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org

[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 --- Comment #5 from GCC Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:b77f17c5feec9614568bf2dee7f7d811465ee4a5 commit r15-1730-gb77f17c5feec9614568bf2dee7f7d811465ee4a5 Author: Richard Biener Date:

[Bug ipa/115701] [11/12/13/14 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 Richard Biener changed: What|Removed |Added Summary|[11/12/13/14/15 Regression] |[11/12/13/14 Regression]

[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 --- Comment #4 from GCC Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:b5c64b413fd5bc03a1a8ef86d005892071e42cbe commit r15-1729-gb5c64b413fd5bc03a1a8ef86d005892071e42cbe Author: Richard Biener Date:

[Bug tree-optimization/115712] [15 regression] Binutils testsuite fails 2 tests (libnew1a.so, libnew1b.so) since r15-571-g1e0ae1f52741f7

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115712 Richard Biener changed: What|Removed |Added Version|unknown |15.0 CC|

[Bug c++/115716] New: internal compiler error: tree check: accessed elt 2 of 'tree_vec' with 1 elts in tsubst, at cp/pt.cc:16364

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115716 Bug ID: 115716 Summary: internal compiler error: tree check: accessed elt 2 of 'tree_vec' with 1 elts in tsubst, at cp/pt.cc:16364 Product: gcc Version: 4.4.7 Status: UN

[Bug tree-optimization/115710] [11/12/13/14/15 Regression] complex abs does not vectorise

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115710 Richard Biener changed: What|Removed |Added CC||rguenth at gcc dot gnu.org --- Comment

[Bug tree-optimization/115709] missed optimisation: vperms not reordered to eliminate

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115709 Richard Biener changed: What|Removed |Added Blocks||53947 CC|

[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 Richard Biener changed: What|Removed |Added CC|rguenth at gcc dot gnu.org | --- Comment #6 from Richard Bi

[Bug target/115526] [14/15 regression] invalid assember emitted for alpha, "Error: duplicate !tlsgd!62"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115526 Andreas K. Huettel changed: What|Removed |Added CC||amacleod at redhat dot com --- Com

[Bug c++/115715] New: gcc seems to incorrectly accept illegal constexpr constructor in virtual inheritance and static template class member

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115715 Bug ID: 115715 Summary: gcc seems to incorrectly accept illegal constexpr constructor in virtual inheritance and static template class member Product: gcc Versio

[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 --- Comment #3 from Richard Biener --- So the main reason for the loss of PTA is that we rewrite 'e' into SSA form only after CCP2 which does the PHI insertion we later attempt to copy to. forwprop then does [local count: 1073741824]: - #

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 100699, which changed state. Bug 100699 Summary: g++ doesn't warn uninitialized field when the class is derived from another class https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100699 What|Removed

[Bug c++/100699] g++ doesn't warn uninitialized field when the class is derived from another class

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100699 Sam James changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[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 Richard Biener changed: What|Removed |Added Version|unknown |15.0 Assignee|unassigned at

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115700 Richard Biener changed: What|Removed |Added Summary|[10/11/12/13/14 regression] |[11/12/13/14 regression]