Tim Prince writes:
> On 5/28/2010 11:14 AM, Ian Lance Taylor wrote:
>>
>> When you run configure, you can specify --with-gnu-as and/or
>> --with-gnu-ld. If you do, the compiler will assume the GNU assembler
>> or linker. If you do not, the compiler will assume that you are not
>> using th
On 5/28/2010 11:14 AM, Ian Lance Taylor wrote:
Quentin Neill writes:
A little off topic, but by what facility does the compiler know the
linker (or assembler for that matter) is gnu?
When you run configure, you can specify --with-gnu-as and/or
--with-gnu-ld. If you do, the compiler
Quentin Neill writes:
> A little off topic, but by what facility does the compiler know the
> linker (or assembler for that matter) is gnu?
When you run configure, you can specify --with-gnu-as and/or
--with-gnu-ld. If you do, the compiler will assume the GNU assembler
or linker. If you do not
On Tue, May 11, 2010 at 6:39 AM, Marc Glisse
wrote:
> On Tue, 11 May 2010, Jakub Jelinek wrote:
>
>> And you can use -Wl,-O1 (pass -O1 to the linker) to let the linker
>> determine optimal size of the hash table (minimum number of collisions
>> for reasonably sized section).
>
> Was it considered
On Tue, 11 May 2010, Ian Lance Taylor wrote:
Marc Glisse writes:
On Tue, 11 May 2010, Jakub Jelinek wrote:
And you can use -Wl,-O1 (pass -O1 to the linker) to let the linker
determine optimal size of the hash table (minimum number of collisions
for reasonably sized section).
Was it consid
Marc Glisse writes:
> On Tue, 11 May 2010, Jakub Jelinek wrote:
>
>> And you can use -Wl,-O1 (pass -O1 to the linker) to let the linker
>> determine optimal size of the hash table (minimum number of collisions
>> for reasonably sized section).
>
> Was it considered enabling this automatically wit
On Tue, 11 May 2010, Jakub Jelinek wrote:
And you can use -Wl,-O1 (pass -O1 to the linker) to let the linker
determine optimal size of the hash table (minimum number of collisions
for reasonably sized section).
Was it considered enabling this automatically with -O3 (or -Ofast) when we
know th
On Mon, May 10, 2010 at 05:15:51PM -0700, Ian Lance Taylor wrote:
> The most obvious change in your data is that the number of hash
> buckets dropped from 4099 to 2053. It's entirely possible that you
> were close to the boundary of when the linker decides to increase the
> number of hash buckets.
Vivek Verma writes:
> I am trying to speedup the load and startup time of a shared
> library. After reading Ulrich Drepper's paper on "How to write shared
> libraries", it seems that the easiest thing to try would be to reduce
> the number of symbols that are globally visible. After carefully
>
