This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: The remaining dubious symbols in libgcc-std.ver
- To: Geert Bosch <bosch at gnat dot com>
- Subject: Re: The remaining dubious symbols in libgcc-std.ver
- From: "Zack Weinberg" <zackw at Stanford dot EDU>
- Date: Mon, 11 Jun 2001 16:58:12 -0700
- Cc: gcc-patches at gcc dot gnu dot org
On Mon, Jun 11, 2001 at 07:50:26PM -0400, Geert Bosch wrote:
>
> On Mon, 11 Jun 2001, Zack Weinberg wrote:
> There are other libgcc symbols used by trampolines on some targets:
> __trampoline, __enable_execute_stack, and possibly others. None of
> them are presently in libgcc-std.ver. I propose to leave them out,
> on the theory that we want to mess with this as little as possible,
> and we can always add them later, but we can never take anything out
> after 3.0 ships.
>
> This will disable function closures on Solaris targets with a
> Sun-recommended security patch installed which disables stack execution.
> Do you propose removing these symbols only from the shared version of
> libgcc, or from the static version as well? I hope not the last, since
> this would make GCC unusable for some kinds of programs.
I propose to leave them as they are right now in 3.0, which means that
they will not be visible in libgcc_s.so. If it is found, later, that
we must make them visible in libgcc_s.so, that change can safely be
made in the 3.0.x series.
--
zw The master came to a yatai which was selling hot dogs. 'What do you
want on your hot dog?' he was asked. 'Nothing,' he replied. Then the
hot dog was enlightened.
-- a koan by Eric Hallstrom