This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Does `-fwhole-program' make sense when compiling shared libraries?
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: Dave Korn <dave dot korn dot cygwin at gmail dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Tue, 18 May 2010 16:13:43 +0200
- Subject: Re: Does `-fwhole-program' make sense when compiling shared libraries?
- References: <4BF1861F.5020406@gmail.com> <4BF1838B.2090603@moene.org> <4BF18A6B.5030603@gmail.com> <4BF2A194.3010601@gmail.com>
> [ hmf. This one got lost to an smtp error when I sent it yesterday. It
> appears there's more or less agreement that at the moment you're supposed to
> manually annotate all external entry points if you want to use -fwhole-program
> on a library. On windows, where we often do that anyway, it looks like it
> would make a great deal of sense to infer externally_visible from dllexport. ]
dllexport is attribute and I think you can quite easilly make frontend hook to
drop externally_visible attribute while handling it. This would indeed make
sense.
Honza