fwiw, I had posted a "all" hidden discussion patch using GCC pragma
visibility for v8 here: http://code.google.com/p/v8/issues/detail?id=411
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options,
On Wed, Jul 29, 2009 at 2:16 PM, Antoine Labour wrote:
> On Wed, Jul 29, 2009 at 10:46 AM, Evan Martin wrote:
>> It turns out that the vast majority of the symbols I mentioned are C++
>> templates.
>> % objdump -CT out/Debug/chrome | wc -l
>> 43740
>> % objdump -CT out/Debug/chrome | egrep -v 'std
On Wed, Jul 29, 2009 at 2:16 PM, Antoine Labour wrote:
> On Wed, Jul 29, 2009 at 10:46 AM, Evan Martin wrote:
> >
> > On Tue, Jul 28, 2009 at 11:18 PM, Brian Ryner wrote:
> > The -fvisibility=hidden flag is maybe supposed to do this (see
> > discussion on http://gcc.gnu.org/wiki/Visibil
On Wed, Jul 29, 2009 at 10:46 AM, Evan Martin wrote:
>
> On Tue, Jul 28, 2009 at 11:18 PM, Brian Ryner wrote:
> The -fvisibility=hidden flag is maybe supposed to do this (see
> discussion on http://gcc.gnu.org/wiki/Visibility ), but I tried
> building both with and without it and fo
On Tue, Jul 28, 2009 at 11:18 PM, Brian Ryner wrote:
>>> > The -fvisibility=hidden flag is maybe supposed to do this (see
>>> > discussion on http://gcc.gnu.org/wiki/Visibility ), but I tried
>>> > building both with and without it and found that:
>>> > - in debug builds, objdump -T shows all of
+bryner for good old times sake, and because he knows about this stuff ;-)
-Darin
On Tue, Jul 28, 2009 at 8:18 PM, Mark Mentovai wrote:
>
> Evan Martin wrote:
> > When we load a plugin any symbols we export come before its symbols.
>
> This doesn't happen on the Mac unless you go out of your w
Evan Martin wrote:
> When we load a plugin any symbols we export come before its symbols.
This doesn't happen on the Mac unless you go out of your way to
arrange for it to happen.
Even so, we do use -fvisiblility=hidden for all Mac builds, because I
like for these things to be well-trimmed anywa
