[Bug c++/82737] [ICE] Compiler segfault on compilation of a certain file (full cause unknown) (file too large for upload, link provided)

2017-11-08 Thread brycm001 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82737 --- Comment #17 from Matti Bryce --- (In reply to Martin Liška from comment #16) > Matti: Any progress with the reduction? Yeah, it's reduced about 20% or so. But it's taken several days just to get this far, so it's going to be quite a while

[Bug c++/82737] [ICE] Compiler segfault on compilation of a certain file (full cause unknown) (file too large for upload, link provided)

2017-10-31 Thread brycm001 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82737 --- Comment #14 from Matti Bryce --- (In reply to Martin Liška from comment #12) > (In reply to Matti Bryce from comment #7) > > (In reply to Martin Liška from comment #5) > > > Confirmed with cross compiler, I reduce a test-case. > > > > I've

[Bug c++/82737] [ICE] Compiler segfault on compilation of a certain file (full cause unknown) (file too large for upload, link provided)

2017-10-29 Thread brycm001 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82737 --- Comment #10 from Matti Bryce --- If anyone knows how to get gcc with debug symbols, that'd be useful, because I could get a better stack trace.

[Bug c++/82737] [ICE] Compiler segfault on compilation of a certain file (full cause unknown) (file too large for upload, link provided)

2017-10-29 Thread brycm001 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82737 --- Comment #9 from Matti Bryce --- (In reply to Martin Liška from comment #2) > Hi. I can't build your pre-process source file. Please follow steps to > reduce the segfault: > https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction > > And

[Bug c++/82737] [ICE] Compiler segfault on compilation of a certain file (full cause unknown) (file too large for upload, link provided)

2017-10-29 Thread brycm001 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82737 --- Comment #8 from Matti Bryce --- Created attachment 42496 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42496=edit Backtrace

[Bug c++/82737] [ICE] Compiler segfault on compilation of a certain file (full cause unknown) (file too large for upload, link provided)

2017-10-29 Thread brycm001 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82737 --- Comment #7 from Matti Bryce --- (In reply to Martin Liška from comment #5) > Confirmed with cross compiler, I reduce a test-case. I've attempted to reduce a test case, but after 2 days of running creduce, the produced file won't generate

[Bug c++/82737] [ICE] Compiler segfault on compilation of a certain file (full cause unknown) (file too large for upload, link provided)

2017-10-27 Thread brycm001 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82737 --- Comment #6 from Matti Bryce --- I have figured out more information. For some reason the build command in the log was (erroneously) listed as -O2, but the actual trigger of the segfault is -O3. I am running creduce right now, but the size

[Bug c++/82737] Compiler segfault on compilation of a certain file (full cause unknown) (file too large for upload, link provided)

2017-10-26 Thread brycm001 at gmail dot com
||r.cpp.i?at=master ||r=file-view-default CC||brycm001 at gmail dot com Host||x86_64-w64-mingw32 Alias

[Bug c++/82737] New: Compiler segfault on compilation of a certain file (full cause unknown) (file too large for upload, link provided)

2017-10-26 Thread brycm001 at gmail dot com
: 7.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: brycm001 at gmail dot com Target Milestone: --- This is a bug that manifests itself in a segfault on an attempt