From: Jakub Jelinek <jakub@redhat.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, "H. Peter Anvin" <hpa@zytor.com>,
GCC Development <gcc@gcc.gnu.org>,
x32-abi@googlegroups.com,
Binutils <binutils@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: x32 psABI draft version 0.2
Date: Thu, 17 Feb 2011 14:29:00 -0000 [thread overview]
Message-ID: <20110217142916.GI13037@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <4D5CEBDE02000078000325A2@vpn.id2.novell.com>
On Thu, Feb 17, 2011 at 08:35:26AM +0000, Jan Beulich wrote:
> >>> On 16.02.11 at 21:04, "H. Peter Anvin" <hpa@zytor.com> wrote:
> > On 02/16/2011 11:22 AM, H.J. Lu wrote:
> >> Hi,
> >>
> >> I updated x32 psABI draft to version 0.2 to change x32 library path
> >> from lib32 to libx32 since lib32 is used for ia32 libraries on Debian,
> >> Ubuntu and other derivative distributions. The new x32 psABI is
> >> available from:
> >>
> >> https://sites.google.com/site/x32abi/home
> >>
> >
> > I'm wondering if we should define a section header flag (sh_flags)
> > and/or an ELF header flag (e_flags) for x32 for the people unhappy about
> > keying it to the ELF class...
>
> Thanks for supporting this!
>
> Besides that I also wonder why all the 64-bit relocations get
> marked as LP64-only. It is clear that some of them can be useful
> in ILP32 as well, and there's no reason to preclude future uses
> even if currently no-one can imagine any.
>
> Furthermore, it seems questionable to continue to require rela
> relocations when for all normal ones (leaving aside the 8- and 16-
> bit ones) the addend can fit in the relocated field.
REL is horrible pain, we shouldn't ever add new REL targets.
Jakub
next prev parent reply other threads:[~2011-02-17 14:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 19:22 H.J. Lu
2011-02-16 20:04 ` H. Peter Anvin
2011-02-16 20:29 ` Roland McGrath
2011-02-16 20:35 ` Chris Metcalf
2011-02-16 20:39 ` Andrew Pinski
2011-02-16 20:46 ` H.J. Lu
2011-02-16 22:13 ` Chris Metcalf
2011-02-17 8:35 ` Jan Beulich
2011-02-17 12:14 ` H.J. Lu
2011-02-17 16:14 ` John Reiser
2011-02-17 17:59 ` Jakub Jelinek
2011-02-17 14:29 ` Jakub Jelinek [this message]
2011-02-17 15:22 ` Jan Hubicka
2011-02-17 15:30 ` H.J. Lu
2011-02-17 15:45 ` Jan Hubicka
2011-02-17 15:49 ` H.J. Lu
2011-02-17 16:10 ` Jan Beulich
2011-02-17 17:59 ` H.J. Lu
2011-02-18 8:10 ` Jan Beulich
2011-02-18 17:53 ` H.J. Lu
2011-02-18 20:32 ` Jan Hubicka
2011-02-21 8:04 ` Jan Beulich
2011-02-17 18:07 ` Jakub Jelinek
2011-02-17 19:56 ` H. Peter Anvin
2011-02-17 22:50 ` Jan Hubicka
2011-02-17 23:00 ` H. Peter Anvin
2011-02-17 23:07 ` Jakub Jelinek
2011-02-18 8:49 ` Jan Beulich
2011-02-17 18:14 ` Joseph S. 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=20110217142916.GI13037@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=JBeulich@novell.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.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).