This is the mail archive of the
mailing list for the GCC project.
Re: Can we speed up the gcc_target structure?
- From: Chris Lattner <sabre at nondot dot org>
- To: "Joseph S. Myers" <jsm at polyomino dot org dot uk>
- Cc: Jan Hubicka <hubicka at ucw dot cz>, Richard Henderson <rth at redhat dot com>,"Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, <ian at wasabisystems dot com>,<gcc at gcc dot gnu dot org>
- Date: Sun, 18 Jan 2004 17:03:31 -0600 (CST)
- Subject: Re: Can we speed up the gcc_target structure?
On Sun, 18 Jan 2004, Joseph S. Myers wrote:
> On Sun, 18 Jan 2004, Jan Hubicka wrote:
> > I suppose this is mostly equivalent to what LLVM have except for the
> > fact that list of symbols with external linkage is boundled in the
> > source itself, instead of being in separate file.
> > Do you have any experience with the separate file having considerable
> > benefits?
> If you could generate the list from a GNU linker script, you could take
> advantage of such a script in any library hiding internal functions that
> way. The obvious example is glibc but I don't know to what extent the
> functions written in assembler would inhibit such optimisations.
Exactly. Also, libstd++ is a great example of a library with a number of
internal symbols, but which is disciplined enough to have a firm grasp of
what is being exported.