public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/46319] LTO plugin test failures with --with-build-config=bootstrap-lto --with-plugin-ld=ld
Date: Wed, 10 Nov 2010 22:53:00 -0000	[thread overview]
Message-ID: <bug-46319-4-WxcrESVmLr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46319-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46319

--- Comment #12 from Dave Korn <davek at gcc dot gnu.org> 2010-11-10 22:52:55 UTC ---
(In reply to comment #11)
> I have verified that
> 
> http://sourceware.org/ml/binutils/2010-11/msg00170.html
> 
> fixes the problem.

Thanks HJ.  I can't self-approve patches to that code but I'll check it in just
as soon as I can, on the branch and head.  (I imagine you want to get on with a
linux-binutils release.)


  parent reply	other threads:[~2010-11-10 22:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 17:10 [Bug lto/46319] New: LTO plugin test failures with --wi th-plugin-ld=ld hjl.tools at gmail dot com
2010-11-05 17:27 ` [Bug lto/46319] LTO plugin test failures with --with-build-config=bootstrap-lto --with-plugin-ld=ld hjl.tools at gmail dot com
2010-11-05 17:44 ` davek at gcc dot gnu.org
2010-11-05 22:59 ` davek at gcc dot gnu.org
2010-11-05 23:28 ` hjl.tools at gmail dot com
2010-11-05 23:30 ` hjl.tools at gmail dot com
2010-11-05 23:31 ` hjl.tools at gmail dot com
2010-11-05 23:33 ` davek at gcc dot gnu.org
2010-11-08  4:53 ` davek at gcc dot gnu.org
2010-11-08  6:27 ` davek at gcc dot gnu.org
2010-11-09 19:32 ` davek at gcc dot gnu.org
2010-11-10 18:01 ` hjl.tools at gmail dot com
2010-11-10 22:53 ` davek at gcc dot gnu.org [this message]
2010-11-11  1:47 ` 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-46319-4-WxcrESVmLr@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).