public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH,trunk+2.21.1] Fix link order problem with LD plugin API.
Date: Sat, 29 Jan 2011 02:59:00 -0000	[thread overview]
Message-ID: <4D4388A3.5000201@gmail.com> (raw)
In-Reply-To: <AANLkTimzu-4HcH55rME9boKrq1HQPo49e-0o7_nA8pHc@mail.gmail.com>

On 29/01/2011 02:45, H.J. Lu wrote:
> On Fri, Jan 28, 2011 at 6:37 PM, Dave Korn <dave.korn.cygwin@gmail.com> wrote:
>> On 29/01/2011 02:05, H.J. Lu wrote:
>>
>>> I run your patch on those new LTO tests. I got relevant failures:
>>>
>>> FAIL: LTO 2
>>> FAIL: LTO 11
>>> FAIL: LTO 8
>>>
>>> Your patch doesn't fix any failures and introduce a new one.
>>>
>>  Thanks for the testcases; I'll see what's going on and respin the patch as
>> needed.
> 
> If you want to fix linker plugin without 2 stage linking, I think you
> should follow
> this gold patch:
> 
> http://sourceware.org/ml/binutils/2011-01/msg00270.html

  Yes, I agree; that's the follow-on I mentioned I'd do next.

    cheers,
      DaveK

  reply	other threads:[~2011-01-29  2:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29  1:23 Dave Korn
2011-01-29  1:45 ` H.J. Lu
2011-01-29  2:01   ` H.J. Lu
2011-01-29  2:05     ` H.J. Lu
2011-01-29  2:11       ` Dave Korn
2011-01-29  2:45         ` H.J. Lu
2011-01-29  2:59           ` Dave Korn [this message]
2011-01-29  4:11       ` Dave Korn
2011-01-29  4:41         ` H.J. Lu
2011-01-31  1:57           ` [PATCH,take 2,trunk+2.21.1] " Dave Korn
2011-02-03  5:12             ` Alan Modra
2011-02-03  5:44               ` Dave Korn
2011-02-03 13:28                 ` Alan Modra
2011-02-05  1:56                   ` Alan Modra

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=4D4388A3.5000201@gmail.com \
    --to=dave.korn.cygwin@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    /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).