This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: followups to your visibility work
- From: Geoffrey Keating <geoffk at geoffk dot org>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: Giovanni Bajo <giovannibajo at libero dot it>, gcc-patches at gcc dot gnu dot org
- Date: 05 Aug 2004 18:39:36 -0700
- Subject: Re: followups to your visibility work
- References: <4112869C.22544.50F7F9F0@localhost><4112C924.9070909@codesourcery.com>
Mark Mitchell <mark@codesourcery.com> writes:
> Niall Douglas wrote:
>
> > One point - you probably still want the check & ignore of non
> > default visibility on global operator new and delete. If code
> > defines this with non-default visibility you get a segfault in GNU
> > ld at link time. And it's very easy to do this accidentally if you
> > use
> >- -fvisibility=hidden.
> >
> Because those are library functions, it should be impossible to do as
> you say; they are created with DECL_VISIBILITY set to
> VISIBILITY_DEFAULT and with DECL_VISIBILITY_SPECIFIED set.
The user is permitted to replace those functions.
(But, GNU ld shouldn't crash, I would suggest fixing that bug instead.)