public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51151] Invalid -Woverflow warning in C++ frontend
Date: Wed, 14 Dec 2011 12:03:00 -0000 [thread overview]
Message-ID: <bug-51151-4-rIRjZt4348@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51151-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51151
Andreas Krebbel <krebbel at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |krebbel at gcc dot gnu.org
--- Comment #3 from Andreas Krebbel <krebbel at gcc dot gnu.org> 2011-12-14 12:00:55 UTC ---
r182175 fixed one failure on s390x but introduced a couple of new fails:
< FAIL: libgomp.c/atomic-2.c execution test
---
> FAIL: libgomp.c++/for-2.C -O0 (test for excess errors)
> WARNING: libgomp.c++/for-2.C -O0 compilation failed to produce executable
> FAIL: libgomp.c++/for-2.C -O1 (test for excess errors)
> WARNING: libgomp.c++/for-2.C -O1 compilation failed to produce executable
> FAIL: libgomp.c++/for-2.C -O2 (test for excess errors)
> WARNING: libgomp.c++/for-2.C -O2 compilation failed to produce executable
> FAIL: libgomp.c++/for-2.C -O3 -fomit-frame-pointer (test for excess errors)
> WARNING: libgomp.c++/for-2.C -O3 -fomit-frame-pointer compilation failed to produce executable
> FAIL: libgomp.c++/for-2.C -O3 -fomit-frame-pointer -funroll-loops (test for excess errors)
> WARNING: libgomp.c++/for-2.C -O3 -fomit-frame-pointer -funroll-loops compilation failed to produce executable
> FAIL: libgomp.c++/for-2.C -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions (test for excess errors)
> WARNING: libgomp.c++/for-2.C -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions compilation failed to produce executable
> FAIL: libgomp.c++/for-2.C -O3 -g (test for excess errors)
> WARNING: libgomp.c++/for-2.C -O3 -g compilation failed to produce executable
> FAIL: libgomp.c++/for-2.C -Os (test for excess errors)
> WARNING: libgomp.c++/for-2.C -Os compilation failed to produce executable
next prev parent reply other threads:[~2011-12-14 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 6:15 [Bug c++/51151] New: " ian at airs dot com
2011-11-17 1:44 ` [Bug c++/51151] " ian at airs dot com
2011-12-09 20:52 ` jason at gcc dot gnu.org
2011-12-14 12:03 ` krebbel at gcc dot gnu.org [this message]
2011-12-14 12:11 ` krebbel at gcc dot gnu.org
2011-12-14 14:33 ` dominiq at lps dot ens.fr
2012-01-02 17:35 ` aaw at gcc dot gnu.org
2012-01-02 17:35 ` paolo.carlini at oracle dot com
2012-01-03 8:36 ` krebbel at gcc dot gnu.org
2012-01-03 8:37 ` krebbel at gcc dot gnu.org
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-51151-4-rIRjZt4348@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).