From: Hongtao <yu171@purdue.edu>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: ipa on all files together
Date: Tue, 02 Nov 2010 00:40:00 -0000 [thread overview]
Message-ID: <4CCF5E02.3060505@purdue.edu> (raw)
In-Reply-To: <AANLkTi=6z4DprSGbLH2E++u1uBFO=ucOV2Y8NoR_P6=8@mail.gmail.com>
On 11/01/10 20:35, Diego Novillo wrote:
> On Mon, Nov 1, 2010 at 19:57, Hongtao <yu171@purdue.edu> wrote:
>> Hi All,
>>
>> While using gcc-4.6 with option -flto, I found that interprocedural
>> analysis were performed on each source file separately. For example for
>> the pass pass_ipa_pta, if we compile two files like :
>> gcc -O -flto f1.c f2.c
>> we have the pass run twice, one for each source file. So is there a way
>> that can perform IPA on all source files together?
> With -combine you used to be able to do this, but it has been removed
> in favour of -flto (actually, I'm not quite sure whether it's been
> removed already, but it's on the chopping block).
>
> With -flto, IPA will be performed on all the files together, as well
> as each file separately. In your example, IPA runs 3 times. Once for
> each f1.c and f2.c, and a third time with both f1.o and f2.o as a
> single translation unit.
Thanks. But can I only keep the third pass, i.e. I want to perform a
pass only on all units together without on each unit separately?
Hongtao
> Diego.
>
next prev parent reply other threads:[~2010-11-02 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 23:57 Hongtao
2010-11-02 0:35 ` Diego Novillo
2010-11-02 0:40 ` Hongtao [this message]
2010-11-02 10:49 ` Richard Guenther
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=4CCF5E02.3060505@purdue.edu \
--to=yu171@purdue.edu \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
/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).