No.

The only game I have that offers any sort of "benchmark" was Wing Commander 3, and with "normal" CPU emulation 64 bit was somewhat faster than 32 bit. On a scale of 0 - 20, with 0 being the fastest and 20 being the slowest, WC reported 13 for x86_64 and 15 for i586.

With "dynamic" core emulation, the 64 bit was unable to reach anywhere near the cycles of 32 bit; 32 bit reached 70% cpu utilization at 40,000 cycles during the graphical wing commander benchmark, while 64bit hit the same performance threshold at about 25,000 cycles, and both reported a cpu speed of zero, which is the fastest the test would register.

i thought the speed should be the same.
not sure where the Bitu is used in a critical speed part.

Qbix wrote:

i thought the speed should be the same.
not sure where the Bitu is used in a critical speed part.

I don't know either, but the graphical display of the rotating ship WC3 uses to benchmark the video speed was very jerky under x86_64, and smooth as silk under i586, after about 20,000 cycles with "dynamic" enabled.

Conversely, Daggerfall FEELS faster under x86_64 at 20k cycles, but only marginally; it's not enough to say for certainty that one is faster than the other.

This was Mandriva 2007, with factory-default installs of the i586 and the x86_64 versions with no modifications whatsoever.

Can anyone suggest any other ways of benchmarking to compare the two versions? Does dosbox have any sort of "fps meter"?

What builds did/are you using? As enabling the dynamic core means you
have a 32bit build. The dynamic core then being slow just means that
the 32bit compatibility mode of the processor is, well, not optimal.

Duke3d, Blood, Redneck Rampage can display the fps so you can compare
speed of different builds/cores when setting cycles=auto.

AH, so the 64 bit version does NOT support the dynamic CPU type?

That probably explains everything I was seeing, then.

I'll see if I can scrape up Duke Nukem and do a FPS comparison.

> AH, so the 64 bit version does NOT support the dynamic CPU type?

Only in the 32bit compatibility mode (32bit builds). If you compile it
as 64bit target it should throw a lot of errors.
If the dynamic core is not available the normal core is used (there might
be some message in the dosbox window).

In duke3d type DNRATE when playing.

OK, you were right.

Duke Nukem shareware, reports 14 - 15 fps at 20,000 cycles under both 64 and 32 bit, normal core.

64 bit reports that dynamic core is unknown option, and remains at 14-15 fps max.

32 bit manages to squeak out 50 fps at about 80% cpu usage with dynamic core.

So that settles that.