public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/63784] [5 Regression] profiledbootstrap failure with bootstrap-lto
Date: Sun, 09 Nov 2014 04:34:00 -0000	[thread overview]
Message-ID: <bug-63784-4-MTRtAG2xFo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63784-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63784

--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
We have a few choices:

1. Build libcc1 with LTO when GCC is configured with
"--with-build-config=bootstrap-lto".  Or
2. Teach libtool to always add -fPIC when linking shared
object to support static archive compiled with LTO.  Or 
3. Don't compile libiberty with LTO.

I tbink #2 is a better choice since the same thing may happen elsewhere.


  parent reply	other threads:[~2014-11-09  4:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-08 21:33 [Bug bootstrap/63784] New: " hjl.tools at gmail dot com
2014-11-09  4:21 ` [Bug bootstrap/63784] " hjl.tools at gmail dot com
2014-11-09  4:34 ` hjl.tools at gmail dot com [this message]
2014-11-09  5:09 ` hjl.tools at gmail dot com
2014-11-09  5:16 ` hjl.tools at gmail dot com
2014-11-09 16:47 ` hjl.tools at gmail dot com
2014-11-10 19:39 ` hjl.tools at gmail dot com
2014-11-21 16:49 ` hjl at gcc dot gnu.org
2014-11-21 16:50 ` hjl.tools at gmail dot com

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-63784-4-MTRtAG2xFo@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).