From: "Jan Beulich" <JBeulich@novell.com>
To: "H.J. Lu" <hjl.tools@gmail.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: Re: x32 psABI draft version 0.2
Date: Mon, 21 Feb 2011 08:04:00 -0000 [thread overview]
Message-ID: <4D622A910200007800032DFE@vpn.id2.novell.com> (raw)
In-Reply-To: <AANLkTi=fL7qVjcyF9JLHaJk6m_d99EaH9YkEv0VJLXKN@mail.gmail.com>
>>> 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).
Jan
next prev parent reply other threads:[~2011-02-21 8:04 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
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 [this message]
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=4D622A910200007800032DFE@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--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).