From: Godmar Back (gback@cs.utah.edu)
Date: Sun Jan 10 1999 - 18:09:08 EST
Forwarded message:
> From oliva@dcc.unicamp.br Sun Jan 10 15:43:22 1999
> Sender: oliva@araguaia.dcc.unicamp.br
> To: Godmar Back <gback@cs.utah.edu>
> Cc: kaffe-core@rufus.w3.org (Kaffe Core Team)
> Subject: Re: Curious Kaffe vs. jdk speed test results under Linux (fwd)
> References: <199901102226.PAA17432@sal.cs.utah.edu>
> From: Alexandre Oliva <oliva@dcc.unicamp.br>
> Date: 10 Jan 1999 20:40:32 -0200
> In-Reply-To: Godmar Back's message of "Sun, 10 Jan 1999 15:26:12 -0700 (MST)"
> Message-ID: <orbtk669b3.fsf@araguaia.dcc.unicamp.br>
> Lines: 23
> User-Agent: Gnus/5.070068 (Pterodactyl Gnus v0.68) XEmacs/20.4 (Emerald)
> Mime-Version: 1.0
>
> On Jan 10, 1999, Godmar Back <gback@cs.utah.edu> wrote:
>
> >>
> >> > It appears that this requires programmers to be very careful about
> >> > avoiding global symbols whenever possible. Or is there a #pragma
> >> > or something that allows programmers to tell the tool chain to not
> >> > include a symbol in this table?
> >>
> >> I think `static' does just that :-)
> >>
>
> > Obviously, I was referring to symbols that are non-static because they're
> > accessed from multiple files within the library but which are not accessed
> > by any files outside the library.
>
> Yep, those will be listed in the symbol table. Anyway, it probably
> doesn't increase the memory usage, since dlopen must lookup the
> symbols in some table too.
>
But only in the case of dynamic libraries. For systems that do not
support dlopen and that do not even have shared libraries, the memory
required to store all external symbols is larger than the memory required
to store only those that we will need to lookup, is it not?
This appears to be a libtool issue. You might want to fix libtool
so that users can selectively exclude symbols from the preopen table.
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:34 EDT