Willus.com Home   |   Archive   |   About  

CONTENTS

I. BACKGROUND
    1. Overview
    2. The Compilers
    3. The Programs
    4. The Systems
    5. Other notes

II. RESULTS
    1. BW1D (C)
    2. BW1D (FOR)
    3. BW2D
    4. FEM2D
    5. LAME

III. SUMMARY
    (User Comments)


Willus.com's 2002 Win32 Compiler Benchmarks:
I. BACKGROUND

5. Other notes

Compile Times

In the benchmark results, I list compile times. These are the total times it took to compile the code using the given compiler and flags on my 1 GHz PIII. Also, the number of lines of code listed is the total lines of source code files (.c, .cpp, .f, .h). This is not the actual number of lines compiled, since the header files must be compiled again and again for each different source module, but it still gives you a sense of how large the code is.

The Intel Compiler

Also, in these benchmarks, you'll see a lot of entries for the Intel compiler (icl or ifl). This is because the Intel compiler has so many compile options that I wanted to try enough of them to be sure I was getting the fastest result with each code and with each CPU type. In particular, the Intel compiler is the only one that can specifically optimize for the P4. In general, I tried to make sure that I covered the same options that Intel and AMD used when compiling their SPEC 2000 benchmarks.

The meanings of some Intel flags:
/QxK Use PIII SSE instructions
/QxW Use P4 SSE-2 instructions
/Qipo Use interprocedural optimizations
/G6 Optimize for PIII
/G7 Optimize for P4

Normalized Scores

A normalized run time is given for each processor type. This is computed by dividing all of the run times in a single processor column by the best run time in that column, and then averaging those values for a given processor. The overall mean normalized score is determined by averaging the normalized scores for the three processor types (PIII, P4, Athlon).

Sort That Data!

As there are so many results, it is useful to be able to sort the data based on the data in a certain column, and so you can. Simply click on a column header in any of the results tables to sort the rows based on the data in that column.

If a code does not have a run time result on a certain system or for a certain compiler, it either means that the code would not run on that system (e.g. certain P4 optimized codes do not run on Athlons or PIIIs), or that the given compiler was not able to compile the code.



<<  Previous: The Systems

Next: BW1D (C)   >>

This page last modified
Thursday, 29-Dec-2011 09:25:00 MST