[Bug lto/96591] [8/9/10/11 Regression] ICE with -flto=auto and -O1: tree code ‘typename_type’ is not supported in LTO streams

2021-02-07 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96591 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug target/98997] New: Linking mismatched -fcf-protection objects generates incorrect code

2021-02-07 Thread luto at kernel dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98997 Bug ID: 98997 Summary: Linking mismatched -fcf-protection objects generates incorrect code Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug libstdc++/98466] Debug Mode iterators for unordered containers do not implement N3644

2021-02-07 Thread fdumont at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98466 François Dumont changed: What|Removed |Added Target Milestone|--- |11.0 Resolution|---

[Bug libstdc++/70303] Value-initialized debug iterators

2021-02-07 Thread fdumont at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70303 François Dumont changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/98532] Use load/store pairs for 2-element vector in memory permutes

2021-02-07 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98532 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2021-02-08

[Bug ada/98996] New: mips64 ada ftbfs

2021-02-07 Thread syq at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98996 Bug ID: 98996 Summary: mips64 ada ftbfs Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada Assignee:

[Bug target/98532] Use load/store pairs for 2-element vector in memory permutes

2021-02-07 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98532 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement CC|

[Bug c++/98995] New: Copy elision not applied to members declared with [[no_unique_address]]

2021-02-07 Thread david at doublewise dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98995 Bug ID: 98995 Summary: Copy elision not applied to members declared with [[no_unique_address]] Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-07 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[Bug c++/98994] New: Empty type with [[no_unique_address]] in union with constructor is not a constant expression

2021-02-07 Thread david at doublewise dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98994 Bug ID: 98994 Summary: Empty type with [[no_unique_address]] in union with constructor is not a constant expression Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug c++/98993] New: Potential memory problem in GCC compiled with ASAN on

2021-02-07 Thread zhan3299 at purdue dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98993 Bug ID: 98993 Summary: Potential memory problem in GCC compiled with ASAN on Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug middle-end/98989] missing -Wfree-nonheap-object freeing std::strings over 15 bytes long

2021-02-07 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98989 Martin Sebor changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c++/98992] New: attribute malloc error associating a member deallocator with an allocator

2021-02-07 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98992 Bug ID: 98992 Summary: attribute malloc error associating a member deallocator with an allocator Product: gcc Version: 11.0 Status: UNCONFIRMED Severity:

[Bug c++/98991] New: ICE: Max. number of generated reload insns per insn is achieved (90)

2021-02-07 Thread zhan3299 at purdue dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98991 Bug ID: 98991 Summary: ICE: Max. number of generated reload insns per insn is achieved (90) Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/98989] missing -Wfree-nonheap-object freeing std::strings over 15 bytes long

2021-02-07 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98989 --- Comment #2 from Martin Sebor --- Not having to annotate _M_create is also helpful when the call isn't inlined. For example, neither of the following functions is diagnosed because in both cases GCC emits a call equivalent to:

[Bug middle-end/98989] missing -Wfree-nonheap-object freeing std::strings over 15 bytes long

2021-02-07 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98989 Martin Sebor changed: What|Removed |Added Keywords||diagnostic --- Comment #1 from Martin

[Bug c++/98990] Internal compiler error when two overloaded functions return `auto &&` and one accepts an `auto` parameter

2021-02-07 Thread david at doublewise dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98990 David Stone changed: What|Removed |Added CC||david at doublewise dot net --- Comment

[Bug c++/98990] New: Internal compiler error when two overloaded functions return `auto &&` and one accepts an `auto` parameter

2021-02-07 Thread david at doublewise dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98990 Bug ID: 98990 Summary: Internal compiler error when two overloaded functions return `auto &&` and one accepts an `auto` parameter Product: gcc Version: 11.0 Status:

[Bug middle-end/98989] New: missing -Wfree-nonheap-object freeing std::strings over 15 bytes long

2021-02-07 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98989 Bug ID: 98989 Summary: missing -Wfree-nonheap-object freeing std::strings over 15 bytes long Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug c++/98988] New: delete is not a constant expression with -fsanitize=undefined

2021-02-07 Thread david at doublewise dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98988 Bug ID: 98988 Summary: delete is not a constant expression with -fsanitize=undefined Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug target/98959] ICE in extract_constrain_insn, at recog.c:2670

2021-02-07 Thread wschmidt at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98959 --- Comment #14 from Bill Schmidt --- We should definitely not be allowing the AltiVec "& ~16" flavors into these patterns. I'm not certain whether your fix is the best way to achieve that, but it could well be; I'll defer to Segher on that.

[Bug c++/79751] Concept placeholder on another concept does not work

2021-02-07 Thread david at doublewise dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79751 David Stone changed: What|Removed |Added CC||david at doublewise dot net --- Comment

[Bug c++/98987] New: Concept subsumption doesn't work with by-value vs. by-reference parameters

2021-02-07 Thread david at doublewise dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98987 Bug ID: 98987 Summary: Concept subsumption doesn't work with by-value vs. by-reference parameters Product: gcc Version: 11.0 Status: UNCONFIRMED Severity:

[Bug bootstrap/98860] [11 Regression] boostrap failure on MinGW-w64 windows 10

2021-02-07 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98860 --- Comment #29 from cqwrteur --- (In reply to Mikael Pettersson from comment #25) > Created attachment 50138 [details] > do not default to dwarf5 on Windows > > I have the same problem with gcc-11 bootstrap failures due to Exec format > errors

[Bug go/98823] go testsuite and timeouts

2021-02-07 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98823 --- Comment #13 from Jakub Jelinek --- I got that with dejagnu 1.6.1.

[Bug go/98823] go testsuite and timeouts

2021-02-07 Thread ian at airs dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98823 --- Comment #12 from Ian Lance Taylor --- Other than the timeout issue, DejaGNU appears to work as expected on my system. After 300 seconds, it will run the shell command "kill -2 $spid" which kills the program. The program issue19182.go does

[Bug rtl-optimization/98986] New: Try matching both orders of commutative RTX operations when there is no canonical order

2021-02-07 Thread ktkachov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98986 Bug ID: 98986 Summary: Try matching both orders of commutative RTX operations when there is no canonical order Product: gcc Version: unknown Status: UNCONFIRMED

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-07 Thread jvdelisle at charter dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #8 from Jerry DeLisle --- (In reply to Jerry DeLisle from comment #6) > (In reply to Bill Long from comment #5) > > Is this fixed in a release version of GCC? > > Submitting patch for approval and will backport as the fix is simple.

[Bug go/98823] go testsuite and timeouts

2021-02-07 Thread ian at airs dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98823 --- Comment #11 from Ian Lance Taylor --- I'm just noting that DejaGNU appears to have a bug in the standard_wait procedure:

[Bug bootstrap/98860] [11 Regression] boostrap failure on MinGW-w64 windows 10

2021-02-07 Thread mikpelinux at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98860 --- Comment #28 from Mikael Pettersson --- (In reply to Brecht Sanders from comment #27) > @Mikael Pettersson, should a similar patch be applied to > gcc/config/i386/mingw-w64.h to fix this same issue in MinGW-w64? cygming.h is used for both

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-07 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 --- Comment #7 from Bill Long --- For our purposes, 10 will be fine.

[Bug libstdc++/98985] New: libstdc++: filesystem::rename not overwriting files on Windows

2021-02-07 Thread m.heinzler at heinzler dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98985 Bug ID: 98985 Summary: libstdc++: filesystem::rename not overwriting files on Windows Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/95647] operator(.eq.) and operator(==) treated differently

2021-02-07 Thread jvdelisle at charter dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at charter dot net ---

[Bug c/97618] undefined reference to LC11 building for target MinGW-w64 32-bit

2021-02-07 Thread brechtsanders at users dot sourceforge.net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97618 --- Comment #4 from Brecht Sanders --- Found a smaller project to reproduce the issue with: building BLAKE3 v0.3.7 from https://github.com/BLAKE3-team/BLAKE3 also has the issue when building with GCC11 for 32-bit MinGW-w64. Here I noticed that

[Bug c/97618] undefined reference to LC11 building for target MinGW-w64 32-bit

2021-02-07 Thread brechtsanders at users dot sourceforge.net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97618 --- Comment #3 from Brecht Sanders --- Issue is till present in GCC 11 snapshot 20210131. When building GCC 11 with GCC 11 the error is still there when trying to build fortran. I also noticed the same error when using GCC 11 to build ccache

[Bug target/98341] [11 Regression] Ada bootstrap fails with Storage_Error stack overflow or erroneous memory access on m68k

2021-02-07 Thread glaubitz at physik dot fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98341 --- Comment #10 from John Paul Adrian Glaubitz --- (In reply to Arnaud Charlet from comment #9) > The problem is somehow specific to m68k, for some unknown reason. There is > nothing target specific in the change, no assumption is made on the >

[Bug target/98341] [11 Regression] Ada bootstrap fails with Storage_Error stack overflow or erroneous memory access on m68k

2021-02-07 Thread charlet at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98341 --- Comment #9 from Arnaud Charlet --- The problem is somehow specific to m68k, for some unknown reason. There is nothing target specific in the change, no assumption is made on the underlying target. What we need now is a debugging session

[Bug target/98341] [11 Regression] Ada bootstrap fails with Storage_Error stack overflow or erroneous memory access on m68k

2021-02-07 Thread glaubitz at physik dot fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98341 --- Comment #8 from John Paul Adrian Glaubitz --- (In reply to Arnaud Charlet from comment #7) > In other words, the bisect result isn't very useful here and I'd recommend > investigating this change from scratch, getting a useful backtrace from

[Bug bootstrap/98860] [11 Regression] boostrap failure on MinGW-w64 windows 10

2021-02-07 Thread brechtsanders at users dot sourceforge.net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98860 --- Comment #27 from Brecht Sanders --- @Mikael Pettersson, should a similar patch be applied to gcc/config/i386/mingw-w64.h to fix this same issue in MinGW-w64?