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

On Mon, Mar 17, 2008 at 7:34 PM, Andrew Haley <[EMAIL PROTECTED]> wrote: > Peter Dolding wrote: > > Ian Lance Taylor wrote: > >> "Peter Dolding" <[EMAIL PROTECTED]> writes: > >> > >> > >>> Since test is in a different object file it gets completely skiped > >>> from optimising even that it sh

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

Peter Dolding wrote: > Ian Lance Taylor wrote: >> "Peter Dolding" <[EMAIL PROTECTED]> 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 >> >

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

Ian Lance Taylor wrote: "Peter Dolding" <[EMAIL PROTECTED]> 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 sta

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

"Peter Dolding" <[EMAIL PROTECTED]> 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

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

Now lets take a simple built. gcc -c test1.c gcc -c test2.c gcc test1.o test2.o -o final --test1.c-- /* of course in real world this would be some complex but solveable function */ int test (int a) { a=a+1; } --test2.c-- #include int test(int a); /* normally in a header somewhere not bothering t