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 ipa/59469] [4.8/4.9 Regression] LLVM build failure with gcc LTO
Date: Sun, 15 Dec 2013 17:11:00 -0000 [thread overview]
Message-ID: <bug-59469-4-0Po3aSIlUY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59469-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59469
--- Comment #13 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Markus Trippelsdorf from comment #12)
> (In reply to Jan Hubicka from comment #10)
> > I also saw in past problems with GNU-ld and comdat symbols becoming static
> > while being comdat somewhere else. Do you use gold or ld? Can you perhaps
> > try to use the other one and see if anything changes?
>
> I use gold. But it doesn't matter in this case, because bfd behaves
> identical.
>
Can you try bfd linker, hjl/linux/release/2.24.51.0.2, from
https://sourceware.org/git/?p=binutils-gdb.git;a=summary
It has a modified LTO bfd linker.
next prev parent reply other threads:[~2013-12-15 17:11 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 13:45 [Bug lto/59469] New: " octoploid at yandex dot com
2013-12-11 13:45 ` [Bug lto/59469] " octoploid at yandex dot com
2013-12-11 19:28 ` octoploid at yandex dot com
2013-12-11 20:49 ` octoploid at yandex dot com
2013-12-11 21:32 ` pinskia at gcc dot gnu.org
2013-12-11 21:35 ` octoploid at yandex dot com
2013-12-13 10:56 ` [Bug ipa/59469] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2013-12-15 14:40 ` hubicka at gcc dot gnu.org
2013-12-15 15:00 ` octoploid at yandex dot com
2013-12-15 15:23 ` hubicka at gcc dot gnu.org
2013-12-15 15:33 ` hubicka at gcc dot gnu.org
2013-12-15 15:47 ` hubicka at gcc dot gnu.org
2013-12-15 15:48 ` octoploid at yandex dot com
2013-12-15 15:50 ` octoploid at yandex dot com
2013-12-15 17:11 ` hjl.tools at gmail dot com [this message]
2013-12-15 17:48 ` hjl.tools at gmail dot com
2013-12-15 18:10 ` hubicka at gcc dot gnu.org
2013-12-15 20:05 ` octoploid at yandex dot com
2013-12-15 23:12 ` steven at gcc dot gnu.org
2013-12-16 13:17 ` hubicka at ucw dot cz
2013-12-16 13:25 ` hubicka at ucw dot cz
2013-12-16 13:46 ` octoploid at yandex dot com
2013-12-16 17:56 ` hubicka at gcc dot gnu.org
2013-12-19 13:24 ` rguenth at gcc dot gnu.org
2014-01-09 20:11 ` rafael.espindola at gmail dot com
2014-01-09 20:34 ` trippels at gcc dot gnu.org
2014-01-09 20:55 ` trippels at gcc dot gnu.org
2014-01-09 20:56 ` trippels at gcc dot gnu.org
2014-01-10 10:06 ` trippels at gcc dot gnu.org
2014-01-10 10:23 ` hubicka at gcc dot gnu.org
2014-01-10 10:25 ` trippels at gcc dot gnu.org
2014-01-10 10:34 ` [Bug c++/59469] " hubicka at gcc dot gnu.org
2014-01-24 17:44 ` jason at gcc dot gnu.org
2014-01-31 18:36 ` jason at gcc dot gnu.org
2014-01-31 18:37 ` [Bug ipa/59469] " jason at gcc dot gnu.org
2014-02-02 15:04 ` trippels at gcc dot gnu.org
2014-02-04 2:22 ` hubicka at gcc dot gnu.org
2014-02-04 5:51 ` hubicka at gcc dot gnu.org
2014-02-04 7:44 ` trippels at gcc dot gnu.org
2014-02-04 7:56 ` trippels at gcc dot gnu.org
2014-02-05 12:20 ` trippels at gcc dot gnu.org
2014-02-05 13:40 ` trippels at gcc dot gnu.org
2014-02-06 17:21 ` hubicka at gcc dot gnu.org
2014-02-07 2:27 ` hubicka at gcc dot gnu.org
2014-02-07 2:28 ` hubicka at gcc dot gnu.org
2014-02-07 2:29 ` hubicka at gcc dot gnu.org
2014-02-07 2:31 ` hubicka 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-59469-4-0Po3aSIlUY@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).