public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Fumiaki Isoya <isoyaf@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: The Extension to ELF
Date: Wed, 08 Aug 2012 06:32:00 -0000	[thread overview]
Message-ID: <CAKOQZ8xJUh8KXt3hG48mVUCQmdcm7TijOiY_zgOFY6p35QNN2g@mail.gmail.com> (raw)
In-Reply-To: <5021FB65.2010704@gmail.com>

On Tue, Aug 7, 2012 at 10:38 PM, Fumiaki Isoya <isoyaf@gmail.com> wrote:

>> I suspect we should make decision of solving all symbols by the
>> calculation.  That is, all symbols should be solved by the
>> calculation of the information that stored in Reverse Polish which
>> consists of constants, other symbols, and their arithmetic.  It
>> also contains the information of shared libraries possibly.  I
>> suppose this decision gives unified implementation of object
>> files, static libraries, and shared libraries.  In fact it will be
>> the extended ELF.

The details matter.

ELF is designed to permit fast program loading at runtime, and to
permit fast linking.  Changing symbol and relocation values to take
general expressions works against that goal.

> I imagine the goal of this infrastructure
> is to provide seamless linking of OO language's object files, C's
> object files, and Asm's object files.

We can already link all these object files together.

I'm sure it is possible to improve on ELF in various ways.  However,
ELF is pretty good.  I very strongly recommend that you understand how
the format works before you attempt to extend it.

Ian

  reply	other threads:[~2012-08-08  6:32 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 [this message]
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

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=CAKOQZ8xJUh8KXt3hG48mVUCQmdcm7TijOiY_zgOFY6p35QNN2g@mail.gmail.com \
    --to=iant@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=isoyaf@gmail.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).