public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/49786] [4.7 Regression] bootstrap failed with bootstrap-profiled Date: Thu, 21 Jul 2011 19:56:00 -0000 [thread overview] Message-ID: <bug-49786-4-YlLXDv9M5s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49786-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49786 --- Comment #15 from Ian Lance Taylor <ian at airs dot com> 2011-07-21 19:56:28 UTC --- Martin: I was able to reproduce it by configuring using --with-ld to point to a newly built version of gold configured with --enable-plugins. Markus: That patch will fix the problem but will do the wrong thing in many cases, because the division will truncate. My exact gcc configure line: --enable-clocale=gnu' '--with-system-zlib' '--enable-shared' '--with-demangler-in-ld' '--enable-cloog-backend=isl' '--with-ppl=/home/iant/gnu/ppl-0.11-install' '--with-cloog=/home/iant/gnu/cloog-0.16.2-install' '--with-build-config=bootstrap-lto' '--with-fpmath=sse' '--with-ld=/usr/local/google/iant/gold/gold-objdir/gold/ld-new' '--enable-languages=c,c++,fortran,java,lto,objc The ld-new mentioned in the --with-ld option was mainline binutils configured with: --enable-gold --enable-plugins The ppl and cloog mentioned in the gcc configure line were downloaded from ftp://gcc.gnu.org/pub/gcc/infrastructure.
next prev parent reply other threads:[~2011-07-21 19:56 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-19 22:33 [Bug bootstrap/49786] New: " hjl.tools at gmail dot com 2011-07-20 0:46 ` [Bug bootstrap/49786] " hjl.tools at gmail dot com 2011-07-20 13:26 ` ian at airs dot com 2011-07-20 13:32 ` hjl.tools at gmail dot com 2011-07-20 14:12 ` ian at airs dot com 2011-07-20 14:17 ` hjl.tools at gmail dot com 2011-07-20 15:30 ` ian at airs dot com 2011-07-20 15:35 ` rguenth at gcc dot gnu.org 2011-07-20 15:37 ` rguenth at gcc dot gnu.org 2011-07-20 15:48 ` jamborm at gcc dot gnu.org 2011-07-20 16:38 ` markus at trippelsdorf dot de 2011-07-20 17:50 ` markus at trippelsdorf dot de 2011-07-20 22:04 ` ian at airs dot com 2011-07-21 13:00 ` jamborm at gcc dot gnu.org 2011-07-21 13:12 ` markus at trippelsdorf dot de 2011-07-21 19:56 ` ian at airs dot com [this message] 2011-07-21 19:58 ` ian at airs dot com 2011-07-22 17:40 ` hjl.tools at gmail dot com 2011-07-26 12:27 ` jamborm at gcc dot gnu.org 2011-07-26 12:28 ` jamborm at gcc dot gnu.org 2011-07-26 12:30 ` jamborm 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-49786-4-YlLXDv9M5s@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: linkBe 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).