From: Cary Coutant <ccoutant@google.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Yinon Ehrlich <yinon.me@gmail.com>, binutils@sourceware.org
Subject: Re: Work done for Incremental link so far ?
Date: Mon, 14 Feb 2011 19:03:00 -0000 [thread overview]
Message-ID: <AANLkTikwFJ_nSuO+BoX_T+OxWaXYT2H+eLTguF--uOnK@mail.gmail.com> (raw)
In-Reply-To: <mcrhbc6bjhz.fsf@google.com>
>> Could you please provide me with pointers for starting - what was
>> already implemented, what are the next TODOs, is there any IRC channel
>> to discuss this work and so on...
>
> There is work being done to support incremental linking in the gold
> linker. Cary Coutant, CC'ed, is doing this work. I think it's mostly a
> set of patches in his own working directory, though. There is some
> design discussion at http://gcc.gnu.org/wiki/GoldIncrementalLinking . I
> don't know how up to date that is.
Yeah, I haven't been sending the patches very regularly, sorry. I'm in
bug-fixing mode right now, and will start feeding patches upstream
shortly, as soon as I get around to doing a git rebase -i to put them
into some semblance of a reasonable order. I did post a set of patches
back in September -- Ian reviewed the first of those and I committed
it, but I'll resubmit the other four.
I need to update the wiki page to reflect the current implementation
-- I've had to add a field to track the section index for global
symbols in relocatable objects, a flag for whether a symbol is defined
or referenced in shared objects, an is_in_system_directory flag for
each input file, and a count of local symbols for each input file.
-cary
next prev parent reply other threads:[~2011-02-14 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 14:53 Yinon Ehrlich
2011-02-14 17:42 ` Ian Lance Taylor
2011-02-14 19:03 ` Cary Coutant [this message]
2011-02-17 8:51 ` Yinon Ehrlich
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=AANLkTikwFJ_nSuO+BoX_T+OxWaXYT2H+eLTguF--uOnK@mail.gmail.com \
--to=ccoutant@google.com \
--cc=binutils@sourceware.org \
--cc=iant@google.com \
--cc=yinon.me@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).