This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: i386 backend
- To: "Jamie Lokier" <egcs at tantalophile dot demon dot co dot uk>
- Subject: RE: i386 backend
- From: "David Rasmussen" <pinkfloydhomer at yahoo dot com>
- Date: Tue, 20 Mar 2001 12:51:30 +0100
- Cc: "David Edelsohn" <dje at watson dot ibm dot com>,"Gcc at Gcc dot Gnu. Org" <gcc at gcc dot gnu dot org>
> -----Original Message-----
> From: Jamie Lokier [mailto:egcs@tantalophile.demon.co.uk]
> Sent: 20. marts 2001 12:50
> To: David Rasmussen
> Cc: David Edelsohn; Gcc@Gcc. Gnu. Org
> Subject: Re: i386 backend
>
>
> David Rasmussen wrote:
> > My problem is that I don't even know that it is in this
> function that gcc
> > differs from the others. It might another place altogether. I
> not only have
> > one critical funtction in this program. The program is rather complex in
> > terms of optimizing. It is hard to isolate problems to just one
> function.
> > There are about 10 critical functions that accounts for 90% of
> the time, and
> > they are interrelated in a very complex manner.
>
> You should be able to run the program under a profiler, which would show
> which of the 10 functions are using more time with GCC than with other
> compilers. Then provide the source and assembly output of the functions
> which really stand out.
>
I will try to do that.
> The behaviour of the program is deterministic, isn't it?
Yes.
David