public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dougmencken at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/61763] [4.9 Regression] bootstrap with -O3 gives comparison failure
Date: Sun, 30 Nov 2014 14:55:00 -0000 [thread overview]
Message-ID: <bug-61763-4-bCfX8TxnDG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61763-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61763
--- Comment #9 from Douglas Mencken <dougmencken at gmail dot com> ---
>How do you actually compile with -O3?
../../flags_O2_to_O3.sh
sed -i '/ CFLAGS_FOR_TARGET=/{n;N;N;N;N;N;N;N;d}' ./configure.ac
sed -i '/ CXXFLAGS_FOR_TARGET=/{n;N;N;N;N;N;N;N;d}' ./configure.ac
sed -i 's/-c -g conftest/-c conftest/' ./configure.ac
sed -i 's/stage1_cflags="-g/stage1_cflags="/' ./configure.ac
Where flags_O2_to_O3.sh script is
http://ftp.osuosl.org/pub/manulix/scripts/service-scripts/flags_O2_to_O3.sh
next prev parent reply other threads:[~2014-11-30 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 19:35 [Bug bootstrap/61763] New: [4.9 Regression] gcc-4.9.0 "Bootstrap comparison failure!" dougmencken at gmail dot com
2014-07-10 8:11 ` [Bug bootstrap/61763] " rguenth at gcc dot gnu.org
2014-07-10 20:19 ` dougmencken at gmail dot com
2014-07-16 13:27 ` jakub at gcc dot gnu.org
2014-07-19 9:56 ` dougmencken at gmail dot com
2014-10-06 5:00 ` dougmencken at gmail dot com
2014-10-30 10:38 ` [Bug bootstrap/61763] [4.9 Regression] gcc-4.9.0 4.9.1 "Bootstrap comparison failure!" when bootstrapping with -O3 jakub at gcc dot gnu.org
2014-11-09 19:48 ` [Bug bootstrap/61763] [4.9 Regression] bootstrap with -O3 gives comparison failure fxcoudert at gcc dot gnu.org
2014-11-24 16:48 ` rguenth at gcc dot gnu.org
2014-11-30 14:55 ` dougmencken at gmail dot com [this message]
2015-06-26 19:52 ` jakub at gcc dot gnu.org
2015-06-26 20:26 ` jakub 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-61763-4-bCfX8TxnDG@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).