public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/60319] wrong code (that hangs) by LTO at -Os and above on x86_64-linux-gnu
Date: Mon, 24 Feb 2014 09:00:00 -0000 [thread overview]
Message-ID: <bug-60319-4-RRfEtw9GNB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60319-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60319
--- Comment #3 from Zhendong Su <su at cs dot ucdavis.edu> ---
(In reply to Richard Biener from comment #1)
> Hmm, I can't reproduce this with 4.8 or trunk but with 4.5, 4.6 and 4.7.
Richard, it still fails for me. Did you use LTO?
$ gcc-trunk -v
Using built-in specs.
COLLECT_GCC=gcc-trunk
COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-trunk/configure --prefix=/usr/local/gcc-trunk
--enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
gcc version 4.9.0 20140223 (experimental) [trunk revision 208062] (GCC)
$
$ gcc-trunk -O0 -c foo.c
$ gcc-trunk -O0 -c main.c
$ gcc-trunk -Os foo.o main.o
$ a.out
$
$ gcc-trunk -flto -O0 -c foo.c
$ gcc-trunk -flto -O0 -c main.c
$ gcc-trunk -flto -Os foo.o main.o
$ a.out
^C
$
$ gcc-4.8 -flto -O0 -c foo.c
$ gcc-4.8 -flto -O0 -c main.c
$ gcc-4.8 -flto -Os foo.o main.o
$ a.out
^C
$
next prev parent reply other threads:[~2014-02-24 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-60319-4@http.gcc.gnu.org/bugzilla/>
2014-02-24 8:37 ` rguenth at gcc dot gnu.org
2014-02-24 8:42 ` rguenth at gcc dot gnu.org
2014-02-24 9:00 ` su at cs dot ucdavis.edu [this message]
2014-02-24 9:20 ` rguenth at gcc dot gnu.org
2014-02-24 15:40 ` su at cs dot ucdavis.edu
2014-02-24 16:36 ` rguenth at gcc dot gnu.org
2014-02-24 17:01 ` rguenth at gcc dot gnu.org
2014-02-25 8:58 ` rguenth at gcc dot gnu.org
2014-02-25 9:00 ` rguenth 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-60319-4-RRfEtw9GNB@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).