Last week I asked...
On Thu, Feb 01, 2001 at 01:51:56PM +, Tim Bunce wrote:
Can anyone recommend extra gcc options to squeeze the last ounce of
performance out of code (perl and apache in this case) on Intel?
I don't mind tying the code down to one cpu type or loosing the ability
to
[Thanks for all the feedback on this from everyone.]
On Thu, Feb 01, 2001 at 05:20:11PM +, G.W. Haywood wrote:
The compiler isn't the place to look for performance gains. Look to
your system architecture, Perl code. See if you can code the things
that get executed the most in C. Use
Can anyone recommend extra gcc options to squeeze the last ounce of
performance out of code (perl and apache in this case) on Intel?
I don't mind tying the code down to one cpu type or loosing the ability
to debug etc. We're already doing -O6 and are looking for more.
I recall Malcom Beattie
Hi Tim,
On Thu, 1 Feb 2001, Tim Bunce wrote:
Can anyone recommend extra gcc options to squeeze the last ounce of
performance out of code (perl and apache in this case) on Intel?
I don't mind tying the code down to one cpu type or loosing the ability
to debug etc. We're already doing -O6
This isn't the best place to ask these questions.
Steve Fink [EMAIL PROTECTED] writes:
And you'd probably want -march=i686 (or whatever CPU you're using).
Not necessarily. gcc and ia32 is weird that way.
I would use whatever Linus co. decided to use for the kernel on that
arch in question.
On Thu, Feb 01, 2001 at 01:51:56PM +, Tim Bunce wrote:
Can anyone recommend extra gcc options to squeeze the last ounce of
performance out of code (perl and apache in this case) on Intel?
I don't mind tying the code down to one cpu type or loosing the ability
to debug etc. We're already
Tim Bunce wrote:
Can anyone recommend extra gcc options to squeeze the last ounce of
performance out of code (perl and apache in this case) on Intel?
I don't mind tying the code down to one cpu type or loosing the ability
to debug etc. We're already doing -O6 and are looking for more.
On Thu, 1 Feb 2001, Tim Bunce wrote:
Can anyone recommend extra gcc options to squeeze the last ounce of
performance out of code (perl and apache in this case) on Intel?
I don't mind tying the code down to one cpu type or loosing the ability
to debug etc. We're already doing -O6 and are
