[Bug c++/65591] G++ should use default constructor for {}-init when possible

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65591 --- Comment #6 from CVS Commits --- The master branch has been updated by Jason Merrill : https://gcc.gnu.org/g:765693be1c8dc91fe612e7a499c5e41ba398ab96 commit r12-6339-g765693be1c8dc91fe612e7a499c5e41ba398ab96 Author: Jason Merrill Date: Th

[Bug c++/65591] G++ should use default constructor for {}-init when possible

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65591 Jason Merrill changed: What|Removed |Added Resolution|--- |DUPLICATE Status|SUSPENDED

[Bug c++/65591] G++ should use default constructor for {}-init when possible

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65591 --- Comment #4 from Andrew Pinski --- Note I thought the patch which fixes PR 92385 would fix this one but instead we are getting an ICE which I filed as PR 103936. I suspect after that is fixed this will also be fixed.

[Bug c++/65591] G++ should use default constructor for {}-init when possible

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65591 Bug 65591 depends on bug 65503, which changed state. Bug 65503 Summary: g++ string array in struct crash https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65503 What|Removed |Added ---

[Bug c++/65591] G++ should use default constructor for {}-init when possible

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65591 --- Comment #3 from Andrew Pinski --- We should be able to do a loop instead of 1000 calls though.

[Bug c++/65591] G++ should use default constructor for {}-init when possible

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65591 Jason Merrill changed: What|Removed |Added Status|NEW |SUSPENDED Depends on|

[Bug c++/65591] G++ should use default constructor for {}-init when possible

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