From: Joseph Myers <joseph@codesourcery.com>
To: "Fāng-ruì Sòng" <maskray@google.com>
Cc: Jan Beulich <jbeulich@suse.com>, <libc-alpha@sourceware.org>,
<binutils@sourceware.org>
Subject: Re: [PATCH] elf: Support DT_RELR relative relocation format [BZ #27924]
Date: Mon, 11 Oct 2021 22:08:51 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2110112206490.1524986@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAFP8O3+oeeJ_ju_uEMF45+40H7Hv5U66OKo1Z6NQ277ujJ3FuA@mail.gmail.com>
On Mon, 11 Oct 2021, Fāng-ruì Sòng via Libc-alpha wrote:
> > While in line with the proposed spec additions I'm afraid the uses of
> > ElfW(Addr) here aren't universally correct: You assume that ELF
> > container type (size) expresses an aspect of the ABI. While this is
> > indeed the case for several arch-es, I think this has been a mistake.
> > IA-64, while meanwhile mostly dead, is (was) an example where 64-bit
> > code can validly live in a 32-bit ELF container (at least as far as
> > the psABI is concerned; I have no idea whether glibc actually
> > followed the spec). There's a separate ELF header flag indicating the
> > ABI, and hence the size of a pointer.
>
> Thanks for chiming in.
>
> As of ia64 buildability, it works for me:
As far as I know, glibc and the Linux kernel never supported ILP32 on ia64
(HP-UX did). But I'm not entirely clear whether the ILP32 ABI is what's
being referred to here (cf. x32, MIPS n32, etc. - ILP32 ABIs using 64-bit
instructions, and 32-bit ELF), or something else.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-10-11 22:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 6:57 Fangrui Song
2021-10-08 15:39 ` Florian Weimer
2021-10-08 16:36 ` Fangrui Song
2021-10-08 19:41 ` Cary Coutant
2021-10-08 16:51 ` H.J. Lu
2021-10-08 17:37 ` Fangrui Song
2021-10-08 17:43 ` H.J. Lu
2021-10-08 18:46 ` Fangrui Song
2021-10-11 7:48 ` Jan Beulich
2021-10-11 18:43 ` Fāng-ruì Sòng
2021-10-11 22:08 ` Joseph Myers [this message]
2021-10-12 8:14 ` Jan Beulich
2021-10-12 8:18 ` Jan Beulich
2021-10-12 14:09 ` H.J. Lu
2021-10-12 16:07 ` Fāng-ruì Sòng
2021-10-13 6:00 ` Jan Beulich
2021-10-13 6:13 ` Fāng-ruì Sòng
2021-10-13 6:18 ` Fāng-ruì Sòng
2021-10-18 7:59 ` Jan Beulich
2021-10-16 20:22 ` Fangrui Song
2021-10-26 23:28 ` Cary Coutant
2021-10-11 21:47 ` Joseph Myers
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=alpine.DEB.2.22.394.2110112206490.1524986@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=libc-alpha@sourceware.org \
--cc=maskray@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).