From: "Cary Coutant" <ccoutant@google.com>
To: "Kenneth Zadeck" <zadeck@naturalbridge.com>
Cc: gcc <gcc@gcc.gnu.org>, "Diego Novillo" <dnovillo@google.com>,
"Ollie Wild" <aaw@google.com>,
"Maddox, Bill" <maddox@google.com>,
"Rafael Espindola" <espindola@google.com>,
"Hubicha, Jan" <jh@suse.cz>
Subject: Re: ln -r and cherry picking.
Date: Fri, 06 Jun 2008 21:08:00 -0000 [thread overview]
Message-ID: <c17be2b30806061407j20228f2bx2bece5f72aa54dae@mail.gmail.com> (raw)
In-Reply-To: <4849A3BE.3000308@naturalbridge.com>
> I think that one of the goals here is to not make that too dependent on elf.
> For instance, we are in the process of getting rid of all of the dwarf.
> After maddox does that, our only dependence on elf will be as a container
> to hold all of the sections.
> Given that gcc is not always an elf compiler, it really is a lot easier to
> invent your own wheel for something like this rather that using elf's wheel
> for the first target and then having to figure out how make someone else
> wheel fit the for the rest of the targets.
This is basic functionality that *every* object file format supports.
I don't think using a symbol and a relocation is going to tie you down
to ELF -- no more so than the idea of using sections to store your
data in.
I also think it's simpler and more deterministic than using a hash.
-cary
prev parent reply other threads:[~2008-06-06 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 15:30 Kenneth Zadeck
2008-06-06 15:34 ` Arnaud Charlet
2008-06-06 15:40 ` Kenneth Zadeck
2008-06-06 20:18 ` Cary Coutant
2008-06-06 20:53 ` Kenneth Zadeck
2008-06-06 21:08 ` Cary Coutant [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=c17be2b30806061407j20228f2bx2bece5f72aa54dae@mail.gmail.com \
--to=ccoutant@google.com \
--cc=aaw@google.com \
--cc=dnovillo@google.com \
--cc=espindola@google.com \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=maddox@google.com \
--cc=zadeck@naturalbridge.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).