From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: LTO and adding extra information from extra passes
Date: Wed, 02 Sep 2009 20:24:00 -0000 [thread overview]
Message-ID: <4A9ED481.9030901@starynkevitch.net> (raw)
In-Reply-To: <84fc9c000909021317r2fdaef4fn6004ff533a33c086@mail.gmail.com>
Richard Guenther wrote:
> On Wed, Sep 2, 2009 at 10:06 PM, Basile
> STARYNKEVITCH<basile@starynkevitch.net> wrote:
>> Hello All,
>>
>> My feeling is that the Link Time Optimisation (LTO) effort should be soon
>> (=is expected to be, or is already) merged inside GCC trunk (future 4.5).
>>
>> Several years ago, I asked if there is any possibility for an additional
>> pass to profit of LTO infrastructure to add some extra data into LTO stuff
>> (which is probably DWARF related inside ELF object files, but I am not sure)
>> and to retrieve it. I remember that the answer was of course not.
[...]
>>
>> I could imagine that a plugin might be interested in adding say some
>> information into the object file (when ordinary compilation for LTO of a
>> single compilation unit happens) and later retrieve it (when link time
>> optimisation occur merging several object files.)
>>
>> A dream case example would be a plugin for whole program static analysis.
>
> The IPA pass infrastructure has all the necessary bits for this.
How do you deal with several compilation units?
I was thinking LTO is designed for that?
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
next prev parent reply other threads:[~2009-09-02 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 20:06 Basile STARYNKEVITCH
2009-09-02 20:18 ` Richard Guenther
2009-09-02 20:24 ` Basile STARYNKEVITCH [this message]
2009-09-02 20:35 ` Richard Guenther
2009-09-02 20:37 ` Basile STARYNKEVITCH
2009-09-03 12:50 ` Diego Novillo
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=4A9ED481.9030901@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@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).