From: Fumiaki Isoya <isoyaf@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: The Extension to ELF
Date: Wed, 08 Aug 2012 17:36:00 -0000 [thread overview]
Message-ID: <5022A350.7070001@gmail.com> (raw)
In-Reply-To: <y0mtxwdqroo.fsf@fche.csb>
> > How is the idea of adopting it as the standard format of GNU Hurd?
>
> I have no opinion on this. Note though that these complex relocations
> are encoded within a standard ELF file (merely using separate
> relocation-type and symbol-type codes). There is no need for an
> OS/kernel to support it, since all the action takes place within the
> assembler and linker.
OK. I do discard my idea trying to cover shared library. But I
believe that if such gas were the standard assembler, anyone will be
able to write lightweight OO compiler language comparatively easily.
- Isoyaf
prev parent reply other threads:[~2012-08-08 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 5:39 Fumiaki Isoya
2012-08-08 6:32 ` Ian Lance Taylor
2012-08-08 7:47 ` Fumiaki Isoya
2012-08-08 11:23 ` Frank Ch. Eigler
2012-08-08 13:24 ` Ian Lance Taylor
2012-08-08 13:34 ` Frank Ch. Eigler
2012-08-08 15:42 ` Fumiaki Isoya
2012-08-08 16:23 ` Frank Ch. Eigler
2012-08-08 17:36 ` Fumiaki Isoya [this message]
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=5022A350.7070001@gmail.com \
--to=isoyaf@gmail.com \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).