public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: binutils Development <binutils@sourceware.org>
Subject: Re: [Patch] bfd elfxx-ia64: share code between elf32 and elf64
Date: Tue, 17 May 2011 13:15:00 -0000	[thread overview]
Message-ID: <BANLkTimmLDU-cB30T2+2rprBw6TV2zpXMw@mail.gmail.com> (raw)
In-Reply-To: <1149AB82-D754-4792-98C1-C677ABE5E712@adacore.com>

On Tue, May 17, 2011 at 6:10 AM, Tristan Gingold <gingold@adacore.com> wrote:
>
> On May 17, 2011, at 3:04 PM, H.J. Lu wrote:
>
>> On Tue, May 17, 2011 at 5:56 AM, Tristan Gingold <gingold@adacore.com> wrote:
>>> Hi,
>>>
>>> some functions of elfxx-ia64.c are in fact the same when compiled for elf32 and for elf64.  This patch adds a new file,
>>> elfxx-ia64.h which declares these functions and compiles them only for elf64.
>>>
>>> No regression for linux/gnu ia64 and hpux ia64.
>>>
>>> This work is in fact preliminary work to support gnu ld on vms/ia64.  Although VMS uses elf64, it doesn't use the same shared library
>>> model.  Its DSO model is derived from the previous vms one (vector based). This made code reuse difficult.
>>>
>>> Ok for trunk ?
>>>
>>
>> Why not do something similar to SPARC/MIPS to put common codes in
>> a new .c file?
>
> That's fine with me.  My proposal would be:
>
> size specific code to elfnn-ia64.c
> common code to elfxx-ia64.c (to match mips and sparc).
>
> Do you agree with this proposal ?
>

I like it.  FWIW, I planned to do it a long ago.

Thanks.

-- 
H.J.

  reply	other threads:[~2011-05-17 13:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 12:56 Tristan Gingold
2011-05-17 13:04 ` H.J. Lu
2011-05-17 13:10   ` Tristan Gingold
2011-05-17 13:15     ` H.J. Lu [this message]
2011-05-17 15:12       ` [Patch v2] " Tristan Gingold
2011-05-23  8:00         ` Ping " Tristan Gingold
2011-05-24 13:50           ` Nick Clifton
2011-05-24 14:17             ` Tristan Gingold
2011-05-25  8:07               ` Nick Clifton
2011-05-25 12:03                 ` Tristan Gingold
2011-07-05 19:06                   ` Aurelien Jarno
2011-07-06  7:00                     ` Tristan Gingold
2011-07-09 18:18                       ` Aurelien Jarno
2011-07-10 11:53                       ` Andreas Schwab
2011-07-11 16:20                         ` H.J. Lu
2011-07-25 13:35                         ` Tristan Gingold
2011-05-17 13:08 ` [Patch] " Andreas Schwab
2011-05-17 13:11   ` Tristan Gingold

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=BANLkTimmLDU-cB30T2+2rprBw6TV2zpXMw@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gingold@adacore.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).