public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/61250] New: Random pch failures on x86_64-apple-darwin13.
Date: Tue, 20 May 2014 09:41:00 -0000 [thread overview]
Message-ID: <bug-61250-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
Bug ID: 61250
Summary: Random pch failures on x86_64-apple-darwin13.
Product: gcc
Version: 4.10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: pch
Assignee: unassigned at gcc dot gnu.org
Reporter: dominiq at lps dot ens.fr
CC: iains at gcc dot gnu.org
Host: x86_64-apple-darwin13
Target: x86_64-apple-darwin13
Build: x86_64-apple-darwin13
When running the test suite on x86_64-apple-darwin13 with -j8 (4 cores, 8
threads), I see random failures for the tests
g++.dg/pch/pch.C
gcc.dg/pch/save-temps-1.c
They are either an ICE:
Internal compiler error: Error reporting routines re-entered.
(may be related to pr59877), or a "program timed out" leading to an "assembly
comparison":
WARNING: program timed out.
FAIL: g++.dg/pch/pch.C -g -I. -Dwith_PCH (test for excess errors)
FAIL: g++.dg/pch/pch.C -g assembly comparison
AFAICT these failures occur for any set of options or -m32/-m64. The number of
failures ranges from 0 to 4/5 and seems (weakly) correlated to the machine load
(-j8+backup).
next reply other threads:[~2014-05-20 9:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 9:41 dominiq at lps dot ens.fr [this message]
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
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
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
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
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
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-61250-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).