This is the mail archive of the
mailing list for the GCC project.
Re: proposal for compilation unil wide alias analyis
- From: Paul Brook <paul at codesourcery dot com>
- To: gcc at gcc dot gnu dot org
- Cc: Kenneth Zadeck <zadeck at naturalbridge dot com>,Mircea Namolaru <NAMOLARU at il dot ibm dot com>, jh at suse dot cz, stuart at apple dot com,geoffk at apple dot com, mark at codesourcery dot com, dpatel at apple dot com,dnovillo at redhat dot com, dberlin at dberlin dot org, dje at watson dot ibm dot com,dalej at apple dot com, ronp at apple dot com, Razya Ladelsky <RAZYA at il dot ibm dot com>,Ayal Zaks <ZAKS at il dot ibm dot com>
- Date: Mon, 28 Jun 2004 14:38:52 +0100
- Subject: Re: proposal for compilation unil wide alias analyis
- Organization: CodeSourcery
- References: <OFDAB522AA.876D1A7C-ONC2256EC1.003E2F55-42256EC1.firstname.lastname@example.org> <40E01254.email@example.com>
On Monday 28 June 2004 13:43, Kenneth Zadeck wrote:
> It depends on what you mean as IPA. For C and I assume Fortran, most
> compilation is single file at a time (except when one is compiling for
> benchmarks). What I noticed was that even at the file at a time mode,
> in C, there was a significant amount of information that was being
> thrown away.
> I would assume that what you are doing is only going to get results for
> compiling whole programs.
> I could be wrong here, but the last time I looked at fortran, it had
> fewer functions per file than C.
Fortran doesn't have file-level scope. Each program unit is entirely
self-contained. If you do have many separate files, You can use "cat" to
merge them together, then compile the result.
 A program unit is a function/subroutine/module/program block. Contained
procedures may be nested within these toplevel blocks.