[Bug c++/95944] Concept diagnostic has multiple copies of irrelevant type and displays correct type incorrectly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95944 ensadc at mailnesia dot com changed: What|Removed |Added CC||ensadc at mailnesia dot com

[Bug c++/95945] New: ICE in poplevel, at cp/decl.c:585

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95945 Bug ID: 95945 Summary: ICE in poplevel, at cp/decl.c:585 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority:

[Bug c++/95518] [coroutines] [[maybe_unused]] does not propagate to actor() and destroy()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95518 --- Comment #4 from CVS Commits --- The releases/gcc-10 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:c3bf482a0e59b9da925b382387686656c3d8839f commit r10-8380-gc3bf482a0e59b9da925b382387686656c3d8839f Author: Iain Sandoe Dat

[Bug c++/95813] Making static member function a coroutine may cause "defined but not used" warning for destroy(frame*) function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95813 --- Comment #3 from CVS Commits --- The releases/gcc-10 branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:c3bf482a0e59b9da925b382387686656c3d8839f commit r10-8380-gc3bf482a0e59b9da925b382387686656c3d8839f Author: Iain Sandoe Dat

[Bug c++/95518] [coroutines] [[maybe_unused]] does not propagate to actor() and destroy()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95518 Iain Sandoe changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug c++/95813] Making static member function a coroutine may cause "defined but not used" warning for destroy(frame*) function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95813 Iain Sandoe changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug rtl-optimization/89310] Poor code generation returning float field from a struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89310 --- Comment #5 from luoxhu at gcc dot gnu.org --- Thanks. I copied the code from movsf_from_si to make a define_insn_and_split for "movsf_from_si2", but we don't have define_insn for rldicr, so I use gen_anddi3 instead, any comment? foo: .LFB0:

[Bug target/95637] Read-only data assigned to `.sdata' rather than `.rodata'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95637 Eric Botcazou changed: What|Removed |Added Status|UNCONFIRMED |NEW CC|

[Bug c++/95519] [coroutines] non-functions for promise_type::return_void not supported

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95519 --- Comment #6 from CVS Commits --- The master branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:31419a80b6bf84b1bf3bcb2489b2e660563f0dfe commit r11-1692-g31419a80b6bf84b1bf3bcb2489b2e660563f0dfe Author: Iain Sandoe Date: Sun

[Bug fortran/53957] Polyhedron 11 benchmark: MP_PROP_DESIGN twice as long as other compiler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53957 --- Comment #20 from Thomas Koenig --- I looked at the output of gfortran -Ofast -funroll-loops -march=native -mtune=native -fopt-info-vec mp_prop_design.f90 2>&1 | wc -l in the Polyhedron testsuite, and I can confirm it really shows much mor

[Bug tree-optimization/95946] New: [meta-bug] auto-parallelization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95946 Bug ID: 95946 Summary: [meta-bug] auto-parallelization Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: tree-optimiza

[Bug tree-optimization/95946] [meta-bug] auto-parallelization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95946 Thomas Koenig changed: What|Removed |Added Depends on||53957, 61121, 40162 Keywords|

[Bug fortran/53957] Polyhedron 11 benchmark: MP_PROP_DESIGN twice as long as other compiler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53957 --- Comment #21 from Thomas Koenig --- Another question: Is there anything left to be done with the vectorizer, or could we remove that dependency?

[Bug tree-optimization/88713] Vectorized code slow vs. flang

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713 --- Comment #57 from Thomas Koenig --- (In reply to H.J. Lu from comment #56) > (In reply to Thomas Koenig from comment #55) > > (In reply to H.J. Lu from comment #45) > > > Created attachment 45510 [details] > > > An updated patch > > > > HJ, d

[Bug fortran/95918] gfortran.dg/char4-subscript.f90 fails for BE architectures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918 --- Comment #5 from Thomas Koenig --- Created attachment 48794 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48794&action=edit patch for the test case, skipping the test on big-endian targets This implements Segher's suggestion to skip th

[Bug fortran/95918] gfortran.dg/char4-subscript.f90 fails for BE architectures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918 --- Comment #6 from Thomas Koenig --- Created attachment 48795 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48795&action=edit Dump file on big-endian system If anybody wants to do the magic for the patterns on big-endian systems, here is

[Bug fortran/95880] [9/10/11 Regression] ICE in gfc_add_type, at fortran/symbol.c:2030 since r11-524-geb069ae8819c3a84

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95880 --- Comment #6 from CVS Commits --- The master branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:f3a8f66a83f8c94f6fbb0233cefba8032f2e4876 commit r11-1693-gf3a8f66a83f8c94f6fbb0233cefba8032f2e4876 Author: Harald Anlauf Date: Su

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #21 from Paul A. Bristow --- I also note that https://en.cppreference.com/w/cpp/io/manip/fixed Notes Hexadecimal floating-point formatting ignores the stream precision specification, as required by the specification of

[Bug fortran/95743] [9/10 Regression] bogus recursive call to nonrecursive procedure with -fcheck=recursion

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95743 Thomas Koenig changed: What|Removed |Added Last reconfirmed||2020-06-28 Status|UNCONFIRME

[Bug c++/95711] namespace alias fails inside coroutine

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95711 --- Comment #3 from CVS Commits --- The master branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:06ed4aae1c2fa84b7050a286d866db4a6def3c36 commit r11-1694-g06ed4aae1c2fa84b7050a286d866db4a6def3c36 Author: Iain Sandoe Date: Sun

[Bug other/32771] Fixincludes should fix realloc in in glibc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32771 Florian Weimer changed: What|Removed |Added Resolution|--- |WORKSFORME CC|

[Bug tree-optimization/88713] Vectorized code slow vs. flang

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713 --- Comment #58 from H.J. Lu --- (In reply to Thomas Koenig from comment #57) > (In reply to H.J. Lu from comment #56) > > (In reply to Thomas Koenig from comment #55) > > > (In reply to H.J. Lu from comment #45) > > > > Created attachment 45510

[Bug fortran/95340] [10/11 Regression] ICE in gfc_match_select_rank, at fortran/match.c:6690

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95340 --- Comment #3 from CVS Commits --- The master branch has been updated by Harald Anlauf : https://gcc.gnu.org/g:b62cac6d92ff251213753475b69ec0b269cb7fae commit r11-1695-gb62cac6d92ff251213753475b69ec0b269cb7fae Author: Harald Anlauf Date: Su

[Bug fortran/95947] New: PACK intrinsic returns blank strings when an allocatable character array with allocatable length is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95947 Bug ID: 95947 Summary: PACK intrinsic returns blank strings when an allocatable character array with allocatable length is used Product: gcc Version: 8.3.1

[Bug fortran/95947] PACK intrinsic returns blank strings when an allocatable character array with allocatable length is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95947 --- Comment #1 from urbanjost at comcast dot net --- Created attachment 48796 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48796&action=edit test using PACK(3f) intrinsic with allocatable variables PACK() intrinsic is returning all blanks

[Bug c++/95948] New: memmove error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95948 Bug ID: 95948 Summary: memmove error Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigne

[Bug fortran/95919] new test base gfortran.dg/char4-subscript.f90 in r11-1654 fails on BE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95919 Thomas Koenig changed: What|Removed |Added Resolution|--- |DUPLICATE CC|

[Bug fortran/95918] gfortran.dg/char4-subscript.f90 fails for BE architectures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918 Thomas Koenig changed: What|Removed |Added CC||seurer at linux dot vnet.ibm.com --- Co

[Bug c++/95948] memmove error

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

[Bug fortran/53957] Polyhedron 11 benchmark: MP_PROP_DESIGN twice as long as other compiler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53957 --- Comment #22 from Anthony --- (In reply to Thomas Koenig from comment #21) > Another question: Is there anything left to be done with the > vectorizer, or could we remove that dependency? thanks for looking into this again for me. i'm surpris

[Bug c++/95949] New: mame build succeeds with -O3 but fails with -O2 and all -O3 flags added manually

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95949 Bug ID: 95949 Summary: mame build succeeds with -O3 but fails with -O2 and all -O3 flags added manually Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severit

[Bug c++/95949] mame build succeeds with -O3 but fails with -O2 and all -O3 flags added manually

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95949 --- Comment #1 from Julian Sikorski --- Created attachment 48797 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48797&action=edit Linking error log

[Bug c++/95949] mame build succeeds with -O3 but fails with -O2 and all -O3 flags added manually

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95949 --- Comment #2 from Julian Sikorski --- The corresponding mame bug: https://github.com/mamedev/mame/issues/6804

[Bug fortran/77871] [8/9/10/11 Regression] [Coarray] [OOP] ICE in gfc_get_caf_token_offset, at fortran/trans-expr.c:1981

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

[Bug tree-optimization/95939] [11 Regression] ice with -O3 in compute_live_loop_exits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95939 Andrew Pinski changed: What|Removed |Added Keywords||ice-on-valid-code Target Milestone|---

[Bug fortran/71706] [8/9/10/11 Regression] [Coarray] ICE on using sync images with integer(kind<>4), with -fcoarray=lib -fcheck=bounds

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

[Bug c++/86568] -Wnonnull warnings should highlight the relevant argument not the closing parenthesis

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86568 --- Comment #6 from CVS Commits --- The master branch has been updated by Martin Sebor : https://gcc.gnu.org/g:75ff24e1920ea6b198350a2961e23175e6108e75 commit r11-1697-g75ff24e1920ea6b198350a2961e23175e6108e75 Author: Martin Sebor Date: Sun

[Bug c++/95950] New: Call to pseudo-destructor does not end the lifetime until C++20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95950 Bug ID: 95950 Summary: Call to pseudo-destructor does not end the lifetime until C++20 Product: gcc Version: 9.1.0 Status: UNCONFIRMED Severity: normal

[Bug c++/95950] Call to pseudo-destructor does not end the lifetime until C++20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95950 Danila Kutenin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/86568] -Wnonnull warnings should highlight the relevant argument not the closing parenthesis

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86568 Martin Sebor changed: What|Removed |Added Status|ASSIGNED|NEW --- Comment #7 from Martin Sebor ---

[Bug c++/95950] Call to pseudo-destructor does not end the lifetime until C++20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95950 --- Comment #2 from Jonathan Wakely --- Right, t.~T() is only a pseudo-destructor for a scalar type. For a class type, it's a destructor.

[Bug fortran/95947] PACK intrinsic returns blank strings when an allocatable character array with allocatable length is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95947 --- Comment #2 from urbanjost at comcast dot net --- Per feedback made test more like a unit test: TEST PROGRAM: character(len=:),allocatable :: m(:) !!NOTE: WORKS WITH len=10 instead of len=: logical :: passed m = [ character(len=10

[Bug c++/95951] New: ICE in extract_call_expr, at cp/call.c:6614

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95951 Bug ID: 95951 Summary: ICE in extract_call_expr, at cp/call.c:6614 Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug libstdc++/95915] [10/11 Regression] std::variant doesn't like types with a defaulted virtual destructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95915 --- Comment #2 from CVS Commits --- The master branch has been updated by Ville Voutilainen : https://gcc.gnu.org/g:24b54628cfa95194a8de4071c28cb56e6e81c08e commit r11-1698-g24b54628cfa95194a8de4071c28cb56e6e81c08e Author: Ville Voutilainen Da

[Bug bootstrap/95952] New: [8.4.1 regression] gcc-8 bootstrap failure on powerpc64-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95952 Bug ID: 95952 Summary: [8.4.1 regression] gcc-8 bootstrap failure on powerpc64-linux Product: gcc Version: 8.4.1 Status: UNCONFIRMED Severity: normal

[Bug c++/95951] ICE in extract_call_expr, at cp/call.c:6614

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95951 Marek Polacek changed: What|Removed |Added Resolution|--- |DUPLICATE CC|

[Bug c++/95629] consteval operator== crashes compiler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95629 Marek Polacek changed: What|Removed |Added CC||bence.kodaj at gmail dot com --- Comment

[Bug tree-optimization/94442] [10/11 regression] Redundant loads/stores emitted at -O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94442 --- Comment #6 from xiezhiheng at huawei dot com --- I'm trying to modify get_inner_reference to handle the case for MEM[ptr, off]. I extract the "off" and add it to the recorded offset, then I build a MEM[ptr, 0] and return it later. Like this

[Bug ada/95953] New: UTF Convert for UTF_16 to UTF_8 fails for values in U+10000 to U+10FFFF.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95953 Bug ID: 95953 Summary: UTF Convert for UTF_16 to UTF_8 fails for values in U+1 to U+10. Product: gcc Version: 7.3.1 Status: UNCONFIRMED Severity: normal

[Bug c++/95954] New: ICE: unexpected expression ‘(a)’ of kind paren_expr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95954 Bug ID: 95954 Summary: ICE: unexpected expression ‘(a)’ of kind paren_expr Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: error-recovery, ice-on-invalid-code Se

[Bug c++/95955] New: ICE: tree check: expected integer_type or enumeral_type or boolean_type or real_type or fixed_point_type, have union_type in int_fits_type_p, at tree.c:8952

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95955 Bug ID: 95955 Summary: ICE: tree check: expected integer_type or enumeral_type or boolean_type or real_type or fixed_point_type, have union_type in int_fits_type_p,

[Bug c++/95956] New: ICE in check_bases, at cp/class.c:1689

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95956 Bug ID: 95956 Summary: ICE in check_bases, at cp/class.c:1689 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: error-recovery, ice-on-invalid-code Severity: norma