public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: GCC Development <gcc@gcc.gnu.org>,
	x32-abi@googlegroups.com, 	Jakub Jelinek <jakub@redhat.com>,
	Binutils <binutils@sourceware.org>,
		GNU C Library <libc-alpha@sourceware.org>,
	Jan Hubicka <hubicka@ucw.cz>, 	"H. Peter Anvin" <hpa@zytor.com>
Subject: x32 psABI draft version 0.3
Date: Mon, 21 Feb 2011 18:08:00 -0000	[thread overview]
Message-ID: <AANLkTimoZPayYthS6y7TFB8W7TpAFU7QOBiBRWgkPYo9@mail.gmail.com> (raw)

On Mon, Feb 21, 2011 at 12:04 AM, Jan Beulich <JBeulich@novell.com> wrote:
>>>> On 18.02.11 at 18:53, "H.J. Lu" <hjl.tools@gmail.com> wrote:
>> How about only allowing REL relocations in executables and DSOes?
>
> That'd be at least part of it, but I'd still prefer not forbidding them
> altogether, but also not requiring an implementation to support
> them (just to repeat it - in a long abandoned new OS of ours we
> had ignored the forbidding, and allowed REL in relocatable objects
> [which were the only objects used there, the loadable ones
> distinguished from "normal" ones by the presence of some OS-
> specific data structures], with the static linker picking the type
> depending on the module's needs).
>

I updated x32 psABI draft to version 0.3 with

---
The AMD64 LP64 ABI architecture uses only Elf64_Rela relocation entries
with explicit addends. The r_addend member serves as the relocation
addend.

The AMD64 X32 ABI architecture uses only Elf32_Rela relocation entries
in relocatable files. Relocations contained within executable files or
shared objects
may use either Elf32_Rela relocation or Elf32_Rel relocation.
---

which is similar to ia64 psABI where rel relocations are only allowed within
executable files or shared objects.


H.J.

                 reply	other threads:[~2011-02-21 18:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=AANLkTimoZPayYthS6y7TFB8W7TpAFU7QOBiBRWgkPYo9@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=JBeulich@novell.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=hpa@zytor.com \
    --cc=hubicka@ucw.cz \
    --cc=jakub@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=x32-abi@googlegroups.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).