public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/45475] target use in libcpp breaks LTO bootstrap
Date: Wed, 14 Dec 2011 10:36:00 -0000 [thread overview]
Message-ID: <bug-45475-4-knvFf5J3HI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45475-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45475
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #13 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-12-14 10:29:00 UTC ---
> Fixed for quite some time
You shouldn't close a PR without installing the testcase in the testsuite. Had
you done so, you would have seen that it isn't fixed at all:
eric@atlantis:~/build/gcc/native32-lto> prev-gcc/xgcc -B prev-gcc -o pr45475
pr45475.c -flto
In file included from pr45475.c:15:0,
from :0:
pr45475.c: In function 'foo':
pr45475.c:16:15: internal compiler error: in convert_move, at expr.c:330
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
lto-wrapper: prev-gcc/xgcc returned 1 exit status
eric@atlantis:~/build/gcc/native32-lto> prev-gcc/xgcc -v
Using built-in specs.
COLLECT_GCC=prev-gcc/xgcc
Target: i586-suse-linux
Configured with: /home/eric/svn/gcc/configure --build=i586-suse-linux
--prefix=/home/eric/install/gcc --with-as=/home/eric/install/gcc/bin/as
--with-ld=/home/eric/install/gcc/bin/ld --enable-languages=c,ada,lto
--enable-stage1-languages=c,ada,lto --with-build-config=bootstrap-lto
--enable-checking=yes,rtl --enable-__cxa_atexit --disable-nls
--disable-libmudflap
Thread model: posix
gcc version 4.7.0 20111214 (experimental) [trunk revision 182322] (GCC)
Thus reopening...
next prev parent reply other threads:[~2011-12-14 10:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45475-4@http.gcc.gnu.org/bugzilla/>
2010-11-29 18:28 ` ebotcazou at gcc dot gnu.org
2010-11-29 18:30 ` ebotcazou at gcc dot gnu.org
2010-11-29 19:06 ` andi-gcc at firstfloor dot org
2010-11-30 12:35 ` rguenth at gcc dot gnu.org
2011-02-01 20:45 ` pinskia at gcc dot gnu.org
2011-02-01 21:19 ` aldot at gcc dot gnu.org
2011-10-07 5:46 ` andi-gcc at firstfloor dot org
2011-12-14 10:36 ` ebotcazou at gcc dot gnu.org [this message]
2012-08-26 23:53 ` pinskia at gcc dot gnu.org
2012-10-15 20:19 ` ebotcazou at gcc dot gnu.org
2012-10-17 9:34 ` [Bug target/45475] target attribute " rguenth at gcc dot gnu.org
2014-09-26 17:59 ` andi-gcc at firstfloor dot org
2010-09-01 9:11 [Bug lto/45475] New: target " andi-gcc at firstfloor dot org
2010-09-01 9:42 ` [Bug lto/45475] " rguenth at gcc dot gnu dot org
2010-09-01 10:16 ` andi-gcc at firstfloor dot org
2010-09-01 10:37 ` andi-gcc at firstfloor dot org
2010-09-01 17:04 ` ak at gcc dot gnu dot org
2010-09-01 17:05 ` andi-gcc at firstfloor dot 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-45475-4-knvFf5J3HI@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).