This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250

--- Comment #8 from howarth at bromo dot med.uc.edu ---
I also noticed that the ICE...

FAIL: g++.dg/pch/pch.C  -O2 -g -I. -Dwith_PCH (internal compiler error)
FAIL: g++.dg/pch/pch.C  -O2 -g -I. -Dwith_PCH (test for excess errors)
FAIL: g++.dg/pch/pch.C  -O2 -g assembly comparison

doesn't seem to produce a log for the crashing compiler in
~/Library/Logs/CrashReporter whereas the crashing testcase executables do. Is
there a trick to building the compiler so that when it crashes a CrashLog will
be produced?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]