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 lto/66029] Build error compiling gcc5.1 using LTO
Date: Tue, 05 May 2015 23:24:00 -0000 [thread overview]
Message-ID: <bug-66029-4-c4SLbIcxoD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66029-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66029
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2015-05-05
Ever confirmed|0 |1
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to JD from comment #0)
> Created attachment 35469 [details]
> complete command line
>
> I compiled gcc5.1 without LTO optimizations and tried to compile it again
> with LTO using the new 5.1 compiler.
>
>
> "openSUSE 13.2 (Harlequin) (x86_64)"
>
> $ gcc -v
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=gcc5.1/lib/gcc/x86_64-unknown-linux-gnu/5.1.0/lto-wrapper
> Target: x86_64-unknown-linux-gnu
> Configured with: ../gcc-5.1.0/configure --prefix=gcc5.1
> --enable-languages=c,c++ --enable-gold=yes --enable-ld=yes --enable-lto
> --enable-bootstrap --disable-multilib
> Thread model: posix
> gcc version 5.1.0 (GCC)
Please configure GCC with --with-build-config=bootstrap-lto for LTO build.
BTW, which linker are you using?
next prev parent reply other threads:[~2015-05-05 23:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 22:21 [Bug lto/66029] New: " t at sharklasers dot com
2015-05-05 22:25 ` [Bug lto/66029] " t at sharklasers dot com
2015-05-05 23:24 ` hjl.tools at gmail dot com [this message]
2015-05-05 23:30 ` pinskia at gcc dot gnu.org
2015-05-06 14:15 ` t at sharklasers dot com
2015-05-06 14:17 ` t at sharklasers dot com
2015-05-06 14:21 ` trippels at gcc dot gnu.org
2015-05-06 14:48 ` hjl.tools at gmail dot com
2015-05-07 15:15 ` trippels at gcc dot gnu.org
2015-05-07 23:58 ` t at sharklasers 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-66029-4-c4SLbIcxoD@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).