* [Bug pch/61250] Random pch failures on x86_64-apple-darwin13.
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
@ 2014-11-11 11:52 ` dominiq at lps dot ens.fr
2014-11-11 11:55 ` fxcoudert at gcc dot gnu.org
` (17 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-11-11 11:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-11-11
CC| |fxcoudert at gmail dot com
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
In https://gcc.gnu.org/ml/gcc-testresults/2014-11/msg01024.html I saw
FAIL: g++.dg/pch/pch.C -O2 -I. -Dwith_PCH (test for excess errors)
FAIL: g++.dg/pch/pch.C -O2 assembly comparison
FAIL: g++.dg/pch/pch.C -O2 -I. -Dwith_PCH (internal compiler error)
FAIL: g++.dg/pch/pch.C -O2 -I. -Dwith_PCH (test for excess errors)
FAIL: g++.dg/pch/pch.C -O2 assembly comparison
FAIL: gcc.dg/pch/save-temps-1.c -O2 -I. -Dwith_PCH (test for excess errors)
FAIL: gcc.dg/pch/save-temps-1.c -O2 assembly comparison
WARNING: program timed out.
FAIL: gcc.dg/pch/save-temps-1.c -O0 -I. -Dwith_PCH (test for excess errors)
FAIL: gcc.dg/pch/save-temps-1.c -O1 -I. -Dwith_PCH (internal compiler error)
FAIL: gcc.dg/pch/save-temps-1.c -O1 -I. -Dwith_PCH (test for excess errors)
FAIL: gcc.dg/pch/save-temps-1.c -O1 assembly comparison
FAIL: gcc.dg/pch/save-temps-1.c -O3 -fomit-frame-pointer -I. -Dwith_PCH
(test for excess errors)
FAIL: gcc.dg/pch/save-temps-1.c -O0 assembly comparison
FAIL: gcc.dg/pch/save-temps-1.c -O3 -fomit-frame-pointer assembly comparison
FX
Are the tests done in parallel? If yes with which value? Are you using "Time
Machine" during the tests?
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin13.
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
2014-11-11 11:52 ` [Bug pch/61250] " dominiq at lps dot ens.fr
@ 2014-11-11 11:55 ` fxcoudert at gcc dot gnu.org
2015-01-03 12:42 ` [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4) dominiq at lps dot ens.fr
` (16 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: fxcoudert at gcc dot gnu.org @ 2014-11-11 11:55 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fxcoudert at gcc dot gnu.org
--- Comment #2 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #1)
> Are the tests done in parallel? If yes with which value? Are you using "Time
> Machine" during the tests?
Yes, tests done in parallel (typically -j6), no Time Machine backup going on
(I'm at home). I know they are random failures, and I have confirmed that they
work well if serial testing is done. I plan to investigate it at some point,
but for now I focused on the main issues :)
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
2014-11-11 11:52 ` [Bug pch/61250] " dominiq at lps dot ens.fr
2014-11-11 11:55 ` fxcoudert at gcc dot gnu.org
@ 2015-01-03 12:42 ` dominiq at lps dot ens.fr
2015-03-07 19:24 ` howarth at bromo dot med.uc.edu
` (15 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: dominiq at lps dot ens.fr @ 2015-01-03 12:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|x86_64-apple-darwin13 |x86_64-apple-darwin1(3|4)
Host|x86_64-apple-darwin13 |x86_64-apple-darwin1(3|4)
Summary|Random pch failures on |Random pch failures on
|x86_64-apple-darwin13. |x86_64-apple-darwin1(3|4).
Build|x86_64-apple-darwin13 |x86_64-apple-darwin1(3|4)
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Also seen on x86_64-apple-darwin14.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (2 preceding siblings ...)
2015-01-03 12:42 ` [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4) dominiq at lps dot ens.fr
@ 2015-03-07 19:24 ` howarth at bromo dot med.uc.edu
2015-03-26 17:58 ` egall at gwmail dot gwu.edu
` (14 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-07 19:24 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
howarth at bromo dot med.uc.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |howarth at bromo dot med.uc.edu
--- Comment #4 from howarth at bromo dot med.uc.edu ---
I see the failure of...
FAIL: g++.dg/pch/pch.C -O2 -I. -Dwith_PCH (internal compiler error)
FAIL: g++.dg/pch/pch.C -O2 -I. -Dwith_PCH (test for excess errors)
Excess errors:
Internal compiler error: Error reporting routines re-entered.
xg++: internal compiler error: Abort trap: 6 (program cc1plus)
randomly with a serial...
make -k check RUNTESTFLAGS="pch.exp=pch.C --target_board=unix'{-m32,-m64}'"
on x86_64-apple-darwin14.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (3 preceding siblings ...)
2015-03-07 19:24 ` howarth at bromo dot med.uc.edu
@ 2015-03-26 17:58 ` egall at gwmail dot gwu.edu
2015-03-26 18:11 ` dominiq at lps dot ens.fr
` (13 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: egall at gwmail dot gwu.edu @ 2015-03-26 17:58 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
Eric Gallager <egall at gwmail dot gwu.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egall at gwmail dot gwu.edu
--- Comment #5 from Eric Gallager <egall at gwmail dot gwu.edu> ---
Does the -Winvalid-pch flag give any extra information?
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (4 preceding siblings ...)
2015-03-26 17:58 ` egall at gwmail dot gwu.edu
@ 2015-03-26 18:11 ` dominiq at lps dot ens.fr
2015-03-26 18:42 ` howarth at bromo dot med.uc.edu
` (12 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: dominiq at lps dot ens.fr @ 2015-03-26 18:11 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Does the -Winvalid-pch flag give any extra information?
AFAICT no.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (5 preceding siblings ...)
2015-03-26 18:11 ` dominiq at lps dot ens.fr
@ 2015-03-26 18:42 ` howarth at bromo dot med.uc.edu
2015-03-26 18:55 ` howarth at bromo dot med.uc.edu
` (11 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-26 18:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #7 from howarth at bromo dot med.uc.edu ---
Is there any sensible approach we can use to try to obtain a backtrace?
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (6 preceding siblings ...)
2015-03-26 18:42 ` howarth at bromo dot med.uc.edu
@ 2015-03-26 18:55 ` howarth at bromo dot med.uc.edu
2015-03-26 19:09 ` howarth at bromo dot med.uc.edu
` (10 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-26 18:55 UTC (permalink / raw)
To: gcc-bugs
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?
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (7 preceding siblings ...)
2015-03-26 18:55 ` howarth at bromo dot med.uc.edu
@ 2015-03-26 19:09 ` howarth at bromo dot med.uc.edu
2015-03-26 19:19 ` howarth at bromo dot med.uc.edu
` (9 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-26 19:09 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #9 from howarth at bromo dot med.uc.edu ---
Unfortunately it doesn't look like the -d option...
`H'
Produce a core dump whenever an error occurs.
is functional on darwin.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (8 preceding siblings ...)
2015-03-26 19:09 ` howarth at bromo dot med.uc.edu
@ 2015-03-26 19:19 ` howarth at bromo dot med.uc.edu
2015-03-26 19:27 ` howarth at bromo dot med.uc.edu
` (8 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-26 19:19 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #10 from howarth at bromo dot med.uc.edu ---
The crashing compiler does leave a crash log in
~/Library/Logs/DiagnosticReports but unfortunately these show...
Backtrace not available
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (9 preceding siblings ...)
2015-03-26 19:19 ` howarth at bromo dot med.uc.edu
@ 2015-03-26 19:27 ` howarth at bromo dot med.uc.edu
2015-03-26 19:27 ` howarth at bromo dot med.uc.edu
` (7 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-26 19:27 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #12 from howarth at bromo dot med.uc.edu ---
To clarify, I am able to debug the core file by executing...
make -k -j8 check RUNTESTFLAGS="pch.exp=pch.C --target_board=unix'{-dH}'"
until I see...
FAIL: g++.dg/pch/pch.C -O2 -I. -Dwith_PCH (internal compiler error)
FAIL: g++.dg/pch/pch.C -O2 -I. -Dwith_PCH (test for excess errors)
FAIL: g++.dg/pch/pch.C -O2 assembly comparison
at which time I find the expected core file added to /cores for use with...
gdb /sw/src/fink.build/gcc5-5.0.0-1/darwin_objdir/gcc/cc1plus /cores/core.4746
which uniformly shows...
#0 0x00007fff96238286 in __pthread_kill ()
#1 0x00007fff9488042f in pthread_kill ()
#2 0x00007fff8e9c1b53 in abort ()
#3 0x0000000100f31530 in linemap_lookup (set=0x1017590f0, line=523) at
../../gcc-5-20150325/libcpp/line-map.c:763
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (10 preceding siblings ...)
2015-03-26 19:27 ` howarth at bromo dot med.uc.edu
@ 2015-03-26 19:27 ` howarth at bromo dot med.uc.edu
2015-03-26 19:42 ` howarth at bromo dot med.uc.edu
` (6 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-26 19:27 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #11 from howarth at bromo dot med.uc.edu ---
It appears that -dH does indeed produce a core in /cores. Using...
gdb /sw/src/fink.build/gcc5-5.0.0-1/darwin_objdir/gcc/cc1plus /cores/core.92484
the bt shows...
#0 0x00007fff96238286 in __pthread_kill ()
#1 0x00007fff9488042f in pthread_kill ()
#2 0x00007fff8e9c1b53 in abort ()
#3 0x0000000100f31530 in linemap_lookup (set=0x10175d000, line=651) at
../../gcc-5-20150325/libcpp/line-map.c:763
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (11 preceding siblings ...)
2015-03-26 19:27 ` howarth at bromo dot med.uc.edu
@ 2015-03-26 19:42 ` howarth at bromo dot med.uc.edu
2015-03-26 20:02 ` howarth at bromo dot med.uc.edu
` (5 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-26 19:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #13 from howarth at bromo dot med.uc.edu ---
The offending line appears to be at...
static const struct line_map*
linemap_macro_map_lookup (struct line_maps *set, source_location line)
{
unsigned int md, mn, mx;
const struct line_map *cached, *result;
if (IS_ADHOC_LOC (line))
line = set->location_adhoc_data_map.data[line & MAX_SOURCE_LOCATION].locus;
linemap_assert (line >= LINEMAPS_MACRO_LOWEST_LOCATION (set)); <=====
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (12 preceding siblings ...)
2015-03-26 19:42 ` howarth at bromo dot med.uc.edu
@ 2015-03-26 20:02 ` howarth at bromo dot med.uc.edu
2015-03-27 3:02 ` howarth at bromo dot med.uc.edu
` (4 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-26 20:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #14 from howarth at bromo dot med.uc.edu ---
Testing https://gcc.gnu.org/ml/gcc-patches/2015-03/msg01334.html in case
correction of the overflow tests eliminates this bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (13 preceding siblings ...)
2015-03-26 20:02 ` howarth at bromo dot med.uc.edu
@ 2015-03-27 3:02 ` howarth at bromo dot med.uc.edu
2015-03-27 3:05 ` howarth at bromo dot med.uc.edu
` (3 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-27 3:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #15 from howarth at bromo dot med.uc.edu ---
(In reply to howarth from comment #14)
> Testing https://gcc.gnu.org/ml/gcc-patches/2015-03/msg01334.html in case
> correction of the overflow tests eliminates this bug.
The proposed patch for correcting overflows doesn't eliminate this bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (14 preceding siblings ...)
2015-03-27 3:02 ` howarth at bromo dot med.uc.edu
@ 2015-03-27 3:05 ` howarth at bromo dot med.uc.edu
2015-03-27 14:04 ` howarth at bromo dot med.uc.edu
` (2 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-27 3:05 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #16 from howarth at bromo dot med.uc.edu ---
(In reply to howarth from comment #15)
> (In reply to howarth from comment #14)
> > Testing https://gcc.gnu.org/ml/gcc-patches/2015-03/msg01334.html in case
> > correction of the overflow tests eliminates this bug.
>
> The proposed patch for correcting overflows doesn't eliminate this bug.
With Jan's patch the failure still appears as...
#0 0x00007fff96238286 in __pthread_kill ()
#1 0x00007fff9488042f in pthread_kill ()
#2 0x00007fff8e9c1b53 in abort ()
#3 0x0000000100f32170 in linemap_lookup (set=0x10175e0f0, line=651) at
../../gcc-5-20150326/libcpp/line-map.c:806
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (15 preceding siblings ...)
2015-03-27 3:05 ` howarth at bromo dot med.uc.edu
@ 2015-03-27 14:04 ` howarth at bromo dot med.uc.edu
2015-03-27 17:46 ` howarth at bromo dot med.uc.edu
2015-03-27 19:23 ` dominiq at lps dot ens.fr
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-27 14:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #17 from howarth at bromo dot med.uc.edu ---
Bug 65550 may be a duplicate of this one.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (16 preceding siblings ...)
2015-03-27 14:04 ` howarth at bromo dot med.uc.edu
@ 2015-03-27 17:46 ` howarth at bromo dot med.uc.edu
2015-03-27 19:23 ` dominiq at lps dot ens.fr
18 siblings, 0 replies; 20+ messages in thread
From: howarth at bromo dot med.uc.edu @ 2015-03-27 17:46 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #18 from howarth at bromo dot med.uc.edu ---
(In reply to howarth from comment #17)
> Bug 65550 may be a duplicate of this one.
Like Bug 65550, the random ICEs in pch.exp are suppressed by building gcc trunk
with --enable-checking=release. In an unrelated issue, I see the parallel make
for this test randomly hang for both the stock build and
--enable-checking=release. I suspect that the pch.exp test harness isn't really
parallel safe.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug pch/61250] Random pch failures on x86_64-apple-darwin1(3|4).
2014-05-20 9:41 [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13 dominiq at lps dot ens.fr
` (17 preceding siblings ...)
2015-03-27 17:46 ` howarth at bromo dot med.uc.edu
@ 2015-03-27 19:23 ` dominiq at lps dot ens.fr
18 siblings, 0 replies; 20+ messages in thread
From: dominiq at lps dot ens.fr @ 2015-03-27 19:23 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #19 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Like Bug 65550, the random ICEs in pch.exp are suppressed by building
> gcc trunk with --enable-checking=release.
This is not true: I have seen the failure with gcc trunk configured with
--enable-checking=release.
> In an unrelated issue, I see the parallel make for this test randomly
> hang for both the stock build and --enable-checking=release.
> I suspect that the pch.exp test harness isn't really parallel safe.
I have also seen the tests hanging in serial test.
I have checked my archives and it seems that the PR appears only on darwin13
and 14.
^ permalink raw reply [flat|nested] 20+ messages in thread