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]

RE: i386 backend


>
> David Rasmussen wrote:-
>
> > I am not sure I understand what you mean. I have a pretty deep
> insight in
> > where my programs "hotspots" are. I have compiled it with many different
> > compilers, profiled it with different profilers etc. But how can I tell
> > where the problem with gcc is from that, when I know nothing about the
> > internals of a compiler?
>
> No-one's asking you for that.  They just want a code example, and the poor
> and improved assembler listings corresponding to it.
>
> In other words, some concreteness.

I can understand that, but as I've explained elsewhere, the process of
isolating code for testcase purposes, is not necesarily a simple one,
especially not if the program in question has a complex interrelationship
between a number of critical functions.

I was hoping that my observations, which are not concrete on purpose, could
stand for themselves, because people who _have_ isolated such code, and who
knows more about gcc that I do, would say: He has a point there. I've been
experiencing the same thing.

But I guess no one here has, then.

David.


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