This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Been Looking how gcc operates there is a major weaknesses in its optimiser.

From: Andrew Haley <aph at redhat dot com>
To: Peter Dolding <oiaohm at gmail dot com>
Cc: Ian Lance Taylor <iant at google dot com>, gcc at gcc dot gnu dot org
Date: Mon, 17 Mar 2008 09:34:02 +0000
Subject: Re: Been Looking how gcc operates there is a major weaknesses in its optimiser.
References: <e7d8f83e0803160632n3e5b5aalf4339859b0e91d23@mail.gmail.com> <m3ve3mldul.fsf@google.com> <47DD9EAB.6070900@gmail.com>

Peter Dolding wrote:
> Ian Lance Taylor wrote:
>> "Peter Dolding" <oiaohm@gmail.com> writes:
>>
>>  
>>> Since test is in a different object file it gets completely skiped
>>> from optimising even that it should be optimised out.
>>>     
>>
>> http://gcc.gnu.org/wiki/LTO_Driver
>>
>> Ian
>>   
> Ok that is half my idea.  Let it sort out at link stage.  But that does
> not cover like libc and dynamic dependencies.

And it can't, either, at least not on GNU/Linux.  When a bug fix is
imported into glibc, every user of glibc immediately benefits.  That's one
of the reasons we don't link statically on that system.  This is far
more important than the performance issue.

Andrew.

Follow-Ups:
- Re: Been Looking how gcc operates there is a major weaknesses in its optimiser.
  - From: Peter Dolding

References:
- Been Looking how gcc operates there is a major weaknesses in its optimiser.
  - From: Peter Dolding
- Re: Been Looking how gcc operates there is a major weaknesses in its optimiser.
  - From: Ian Lance Taylor
- Re: Been Looking how gcc operates there is a major weaknesses in its optimiser.
  - From: Peter Dolding

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]