are you interested in a different compilation model for IPA? I.e. say,
matching .I file for each .c input file? What is the purpose of your
studying the .I files?
The original purpose is to enable parallel compilation by the later backend
phases. I believe partitioning of the call graph to maximize parallelism
(likely minium edges among the subgraph partitions) is the motivation.
I don't believe above description is documented anywhere.
Sun
On Tue, Jul 6, 2010 at 4:17 PM, Li Shengmei <lis...@gmail.com> wrote:
> Hi,all
> I want to know how the .I files which are generated during IPA. The
> debug document of IPA is "TBD" in the doc of Open64.
> Does anyone know the generation of .I files or give some suggestions
> about studying it?
> What is the principle of generating .I files? How can I control the
> generation?
>
> Thanks a lot,
> May
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Open64-devel mailing list
> Open64-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/open64-devel
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Open64-devel mailing list
Open64-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open64-devel
