This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Can we speed up the gcc_target structure?

From: Jakub Jelinek <jakub at redhat dot com>
To: Jan Hubicka <hubicka at ucw dot cz>
Cc: Chris Lattner <sabre at nondot dot org>, Jan Hubicka <jh at suse 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 22:26:47 +0100
Subject: Re: Can we speed up the gcc_target structure?
References: <20040118224838.GL5119@kam.mff.cuni.cz> <Pine.LNX.4.44.0401181708570.18959-100000@nondot.org> <20040118232701.GA31365@atrey.karlin.mff.cuni.cz>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Mon, Jan 19, 2004 at 12:27:01AM +0100, Jan Hubicka wrote:
> I think that at least glibc has special marker for each external symbol
> so it is not concern there.

No.  glibc has some markers for internal symbols which are not static
(__attribute__((visibility ("hidden"))) ).
But in the end what is really exported is controlled by the linker version
script.

	Jakub

References:
- Re: Can we speed up the gcc_target structure?
  - From: Jan Hubicka
- Re: Can we speed up the gcc_target structure?
  - From: Chris Lattner
- Re: Can we speed up the gcc_target structure?
  - From: Jan Hubicka

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]