This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Can we speed up the gcc_target structure?
- From: Chris Lattner <sabre at nondot dot org>
- To: Jan Hubicka <jh at suse dot cz>
- 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>, "Joseph S. Myers" <jsm at polyomino dot org dot uk>
- Date: Sun, 18 Jan 2004 17:09:49 -0600 (CST)
- Subject: Re: Can we speed up the gcc_target structure?
On Sun, 18 Jan 2004, Jan Hubicka wrote:
> If you mark no symbols via special attribute, only main should be
> external. If you mark more, you get more.
Ok, I see.
> > > 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?
> >
> > I'm not sure if I understand what you mean here, can you please clarify?
>
> You mentioned that instead of using attribute in the source file, you
> get list of functions. From here the lists are comming?
We use an external file (a linker script basically) to decide the list.
You can also specify the list with a -Wl option.
> > (for example) dynamically load shared objects that call back into the main
> > program. People will get unhappy if 'gimp' doesn't work in this mode, for
> > example.
>
> I expect people to just mark the interface functions via the attribute.
Ok, great. :)
-Chris
--
http://llvm.cs.uiuc.edu/
http://www.nondot.org/~sabre/Projects/