public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Roland McGrath <mcgrathr@google.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] BFD vector for elf32-i386-nacl
Date: Wed, 27 Jul 2011 01:06:00 -0000	[thread overview]
Message-ID: <CAMe9rOpPkgyERzx4nJOVH0+MA_jNZv-eaN+=DDFieghtbSMF1g@mail.gmail.com> (raw)
In-Reply-To: <CAB=4xhq7DZ55saQZUNb3ZCFdiwU_VAZtp8=eCVFq45x6arS8BQ@mail.gmail.com>

On Tue, Jul 26, 2011 at 4:05 PM, Roland McGrath <mcgrathr@google.com> wrote:
> I could make the struct of PLT-generation parameters hang off struct
> elf_i386_link_hash_table instead of hanging off struct
> elf_backend_data.
> That is more costly and less clean IMHO, but it is more similar to the
> existing terrible kludges used for vxworks.
> I don't think it's reasonable to ask that I completely revamp the
> vxworks support in a clean fashion, since I have nothing to do with
> vxworks.
> Would that make you happy?
> Do other folks have feedback here?

I was not very happy about the way how vxworks was handled.
But there was no better proposal at the time.   I think it will be
nice to clean it up this time.

Thanks.

-- 
H.J.

  reply	other threads:[~2011-07-26 23:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 21:20 Roland McGrath
2011-07-26 21:23 ` H.J. Lu
2011-07-26 21:36   ` Roland McGrath
2011-07-26 23:05     ` H.J. Lu
     [not found]       ` <CAB=4xhp0Ctn3Kwq9JOQ5nWoN8NH_ejVLE0qJ61z2vK2L6fwjOA@mail.gmail.com>
2011-07-26 23:09         ` H.J. Lu
2011-07-26 23:11           ` Roland McGrath
2011-07-27  1:06             ` H.J. Lu [this message]
2011-07-27  6:31               ` Roland McGrath
2011-07-27 20:59                 ` Roland McGrath
2011-07-27 21:49                   ` H.J. Lu

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='CAMe9rOpPkgyERzx4nJOVH0+MA_jNZv-eaN+=DDFieghtbSMF1g@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=mcgrathr@google.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).