This is the mail archive of the
mailing list for the GCC project.
Re: PATCH: PR middle-end/20297: #pragma GCC visibility isn't properlyhandled for builtin functions
- From: Roger Sayle <roger at eyesopen dot com>
- To: "H. J. Lu" <hjl at lucon dot org>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Thu, 3 Mar 2005 20:49:52 -0700 (MST)
- Subject: Re: PATCH: PR middle-end/20297: #pragma GCC visibility isn't properlyhandled for builtin functions
On Thu, 3 Mar 2005, H. J. Lu wrote:
> 2005-03-03 H.J. Lu <firstname.lastname@example.org>
> PR middle-end/20297
> * builtins.c (expand_builtin_1): Renamed from expand_builtin.
> (expand_builtin): Save/restore default_visibility and
> visibility_options.inpragma when calling expand_builtin_1.
Can you explain exactly how this helps? expand_builtin is called
in the middle-end during RTL expansion for calls *to* intrinsic
functions. I don't understand how this could possibly affect the
visibility of a "memcpy" symbol. expand_builtin doesn't emit any
symbols, and often doesn't reference any.
Isn't "pragma visibility" a front-end concept that should be attached
Confused of Santa Fe,