CodeWarrior Benchmark for Windows

SDL Development
#1

Compiler: VC6 and CodeWarrior 5.3
Optimizations: Pentium Pro CPU, MMX Instructions, Release Versions.

Source:
Fire Demo from http://www.xdr.com/dash

Both compilers resulted in a FPS of 36. The SDL.dll was built with VC6 in
release mode and used with both compilers. Does anyone know of a makefile
for SDL for Code Warrior for Windows?

-Ryan

#2

Win2k Pro
256 MB RAM
Geforce 2 GTS
P3 733

Compiler: VC6 and CodeWarrior 5.3
Optimizations: Pentium Pro CPU, MMX Instructions, Release Versions.

Source:
Fire Demo from http://www.xdr.com/dash

Both compilers resulted in a FPS of 36.

36 fps with that monster setup? It seems likely that this isn’t a good
benchmark. As always when benchmarking, know what you are really
measuring.

#3

Hmmm, 36 is what it is.

“Mattias Engdeg?rd” wrote in message
news:200008191422.QAA10829 at octans.nada.kth.se…> > Win2k Pro

256 MB RAM
Geforce 2 GTS
P3 733

Compiler: VC6 and CodeWarrior 5.3
Optimizations: Pentium Pro CPU, MMX Instructions, Release Versions.

Source:
Fire Demo from http://www.xdr.com/dash

Both compilers resulted in a FPS of 36.

36 fps with that monster setup? It seems likely that this isn’t a good
benchmark. As always when benchmarking, know what you are really
measuring.

#4

This is interesting…

Under vc6 release settings I get 88 fps
Under codewarrior 5.3 with 3dNow optimisations i get 70 fps
but with 3dnow turned off i get 63 fps …

these examples were all linked against sdl 1.1.4 compiled under vc6

The machine is an athlon 850 with 512 Mb of ram and a geforce2.

However the geforce should no make a huge difference as there is no OGL in
this example.

I seems that when ever i have in the past tried to link source compiled in
metrowerks against code warrior i have problems, be it performance or just
compiler errors. I have never been able to build the sdl.dll completely
under code warrior due rather intersting errors( mainly winapi related
errors … sigh the sillines will never stop…)

I have also noticed that in the first 30 seconds of execution or so the
programs runs slow … and then speeds up… in this period if you terminate
you will only get approx 40fps… perhaps if it is intended to be a
benchmark, i may be an idea to execute a certain amount of frames and then
take the timing …

dunno… thats all i have to say …

regards John.

At 10:29 19/08/00 -0700, you wrote:

Hmmm, 36 is what it is.

“Mattias Engdeg?rd” wrote in message
news:200008191422.QAA10829 at octans.nada.kth.se…

Win2k Pro
256 MB RAM
Geforce 2 GTS
P3 733

Compiler: VC6 and CodeWarrior 5.3
Optimizations: Pentium Pro CPU, MMX Instructions, Release Versions.

Source:
Fire Demo from http://www.xdr.com/dash

Both compilers resulted in a FPS of 36.

36 fps with that monster setup? It seems likely that this isn’t a good
benchmark. As always when benchmarking, know what you are really
measuring.

yAKMOOSE iNTERGALACTIC

[code brokers]
http://www.yakmoose.org.nz

#5

I seems that when ever i have in the past tried to link source compiled in
metrowerks against code warrior i have problems, be it performance or just
compiler errors. I have never been able to build the sdl.dll completely
under code warrior due rather intersting errors( mainly winapi related
errors … sigh the sillines will never stop…)

Could you send me the errors directly at @slouken?

I have also noticed that in the first 30 seconds of execution or so the
programs runs slow … and then speeds up… in this period if you terminate
you will only get approx 40fps… perhaps if it is intended to be a
benchmark, i may be an idea to execute a certain amount of frames and then
take the timing …

Does it run visibly slower? I haven’t found this to be the case in general.
Possibly your FPS algorithm has a bug?

See ya,
-Sam Lantinga, Lead Programmer, Loki Entertainment Software