Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at norgg dot org
Target Milestone: ---
Created attachment 38163
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38163&action=edit
Minimal testcase
The attached code c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70515
--- Comment #1 from Norgg ---
Created attachment 38164
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38164&action=edit
Preprocessed file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70515
Norgg changed:
What|Removed |Added
CC||gcc at norgg dot org
--- Comment #4 from Norgg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70515
--- Comment #5 from Norgg ---
Created attachment 40994
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40994&action=edit
gcc -v output for gcc 6.2.0
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at norgg dot org
Target Milestone: ---
Created attachment 36380
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36380&action=edit
Minimal testcase
Minimal te
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67699
--- Comment #1 from Norgg ---
Created attachment 36381
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36381&action=edit
Reduced testcase with const instead of constexpr
Futher testing by slowriot found that you can change the constexpr to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67699
--- Comment #2 from Norgg ---
It seems the -fmerge-all-constants isn't necessary to cause the segfault either
any more, although it was in an earlier larger test case.
Minimal command line to reproduce is now:
$ g++ const_crash.cpp -flto
const_c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67699
--- Comment #3 from Norgg ---
Created attachment 36382
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36382&action=edit
Preprocessed file
