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

 > 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'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.

Thanks for your reply.

I don't necessarily have a thought special to ELF.  I merely thought
vaguely "it will become such a form, supposing it realizes".  If
required, even if it will become a completely different format from
ELF, I don't care.

I showed example.

 > Point_do6       .define Object_MMAX .+ 4

What I hope is that this definition is going to be stored in .o file
as the following form.

[Point_do6] [Object_MAX] [4] [+] [!]

My main hope is to keep the principle "What is necessary is to
re-compile only the source files you touched".  I don't care at all if
I must convert the execution file or library file from different
format to ELF after linking or archiving.

  reply	other threads:[~2012-08-08  7:47 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 [this message]
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=50221992.9020407@gmail.com \
    --to=isoyaf@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.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).