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 bootstrap/68041] [6 Regression] Bootstrap broken on x86_64-apple-darwin14 at revision r229119
Date: Wed, 21 Oct 2015 14:08:00 -0000 [thread overview]
Message-ID: <bug-68041-4-nHMAIarLBP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68041-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68041
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
With the patch in comment 2, bootstrap completed without any problem.
Preliminary tests for g++ and asan
=== g++ Summary for unix/-m64 ===
# of expected passes 1007
# of unexpected failures 14
# of unsupported tests 179
=== g++ Summary ===
# of expected passes 2021
# of unexpected failures 21
# of unsupported tests 358
the failures are
FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O0 output pattern test
FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O1 output pattern test
FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O2 output pattern test
FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O3 -g output pattern test
FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -Os output pattern test
FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O2 -flto
-flto-partition=none output pattern test
FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O2 -flto output pattern
test
for both -m32 and -m64, and
FAIL: c-c++-common/asan/memcmp-1.c -O0 output pattern test
FAIL: c-c++-common/asan/memcmp-1.c -O1 output pattern test
FAIL: c-c++-common/asan/memcmp-1.c -O2 output pattern test
FAIL: c-c++-common/asan/memcmp-1.c -O3 -g output pattern test
FAIL: c-c++-common/asan/memcmp-1.c -Os output pattern test
FAIL: c-c++-common/asan/memcmp-1.c -O2 -flto -flto-partition=none output
pattern test
FAIL: c-c++-common/asan/memcmp-1.c -O2 -flto output pattern test
for -m64 only.
How many lines of the output do you need to adjust the regexps?
Further tests for ubsan and gcc in progress.
next prev parent reply other threads:[~2015-10-21 14:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 10:41 [Bug bootstrap/68041] New: " dominiq at lps dot ens.fr
2015-10-21 10:49 ` [Bug bootstrap/68041] " chefmax at gcc dot gnu.org
2015-10-21 11:16 ` chefmax at gcc dot gnu.org
2015-10-21 11:49 ` dominiq at lps dot ens.fr
2015-10-21 11:59 ` rguenth at gcc dot gnu.org
2015-10-21 14:08 ` dominiq at lps dot ens.fr [this message]
2015-10-21 14:44 ` dominiq at lps dot ens.fr
2015-10-21 15:52 ` dominiq at lps dot ens.fr
2015-10-21 16:14 ` chefmax at gcc dot gnu.org
2015-10-21 16:18 ` dominiq at lps dot ens.fr
2015-10-22 9:42 ` chefmax at gcc dot gnu.org
2015-10-22 9:47 ` chefmax at gcc dot gnu.org
2015-10-22 9:50 ` chefmax at gcc dot gnu.org
2015-10-22 15:48 ` 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-68041-4-nHMAIarLBP@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).