James E Wilson wrote:

Daniel Berlin wrote:

A bunch of random code #ifdef KEY'd


FYI Pathscale was formerly known as Key Research. So the KEY probably wouldn't mean anything special here, it is likely just a marker for local changes.

I heard a lot of this compiler and expected a better results for it. Using -O2 -mtune=nocona for gcc4 and -O2 -mtune=em64t for open64 on em64t machine in 32-bit mode, I found preliminarily that pathscale compiler generates about 10% worse and 30% larger code (text segment) for SPECInt2000. It is also 70% slower than gcc4. I just hope results for 64-bit mode, amd machine, or SPECFP2000 are better.

Vlad


Reply via email to