@corto

Just a small correction, the right GCC compiler switch to use is -mcpu=440fp otherwise the compiler will generate code without FPU support.

_________________
Massimiliano Tretene, ACube Systems, Soft3

@m3x

Quote:

m3x wrote: @corto Just a small correction, the right GCC compiler switch to use is -mcpu=440fp otherwise the compiler will generate code without FPU support.

You're right, I use 440fp, I wrote "440" without checking the real syntax I used.

About the perflib features included in newlib : I was not aware, nice to know !

@m3x

OK, thank you. I haven't noticed that thread or i don't remember it :P

_________________
retired

@corto

Quote:

Could you give me the procedure to run the Doom benchmark please ?

Of course.

The Doom benchmark thread on AW

I tested DosBox for Windows, simple core, auto CPU cycles.

Edit:
I think the obvious difference between DosBox (40 FPS) and Bochs (20 FPS) on the same hardware in the Doom benchmark is based on much faster GFX emulation in DosBox. GFX benchmarks I did show that DosBox (Windows) is in some cases 3-4 times faster than Bochs, some GFX operations in Bochs are even slower than on original S3 VLB GFX card (eg. fades are toooooo slooooow).

Last edited by pavlor on 08-Jul-2011 at 02:44 PM.

@m3x

Quote:

As I said in another thread while back, there is no need to use the IBM perflibs anymore, the same functionalities are include within newlib.

Does this mean that the 24 DSP functions will be used automatically when compiling with -440fp or is it necessary to use them as it has do be done with Altivec ?

Last edited by K-L on 08-Jul-2011 at 03:53 PM.
Last edited by K-L on 08-Jul-2011 at 03:52 PM.

_________________
PowerMac G5 2,7Ghz - 2GB - Radeon 9650 - MorphOS 3.14
AmigaONE X1000, 2GB, Sapphire Radeon HD 7700
FPGA Replay + DB 68060 at 85Mhz

It seems that DirectX based games work only with dynamic CPU core (full core is not present in the current version - my mistake), so no Windows games on DosBox for OS4 or MorphOS.

However, current AmigaOS hardware is not fast enough for these games, possibility to run Windows games would be interesting only for some future computers (eg. X1000). Best solution would be to port QEMU...

@K-L
With the compilation option -mcpu=440fp, I would say yes, the DSP instructions are used. But again, that doesn't help with dosbox.

dosbox 0.74
Hey guys, I am short in time now to prepare a full package but dosbox 0.74 exe is here. I had no time to test with Doom but this is a working version. It would be great if you could test it and provide feedback. So, if you think it is good enough, I will release a clean archive later. Sorry for the delay but at least you can enjoy it now.

@corto

I tried with the default conf (3000 cycles) provided in the archive found on OS4depot (0.73a) with shareware doom :
0.73a : cpu 55-58%
0.74 : cpu 53-55%

that is at the start of a new game (and with default sound) on my A1G4+AOS4.1u2

so a little improvement

thanks for this new release !

PS: I am wondering what is the max cycles I should put for my computer

@corto

Quote:

With the compilation option -mcpu=440fp, I would say yes, the DSP instructions are used. But again, that doesn't help with dosbox.

Shouldn't this be -march=440fp if you want CPU specific instructions to be used? AFAICT from doing some googling the -mcpu option is the same as -mtune which only tunes the code to a specific CPU (may change order of some instructions f.e. to be more optimal) but still generates generic code unless -march is specified as well.

Anyway I doubt that GCC will be able to make any good use of the DSP instructions in this way. More likely you need to write assembler code to use these instructions if you want to see any significant speed increase.

@lionstorm

Quote:

PS: I am wondering what is the max cycles I should put for my computer

I think your computer can reach 5400 CPU cycles (rougly 80386DX 40 MHz) with such demanding game like Doom. I use 4500 CPU cycles - enough for most of my old DOS games.

@pavlor

thx, will update my .conf accordingly

DosBox 0.74 has a (new) keyboard issue: try typing C:

_________________
: AmigaOneXE (unmod.) 750FX/512 MB +stuff & AmigaOS 4.(0|1)
: A1200/68060&96MB/SCSI/EM1200-Voodoo3 & OS 3.5
: A500/1MB
: Pegasos (ff) 512 MB & MorphOS
Praise seitan.

My next eperiment with DosBox was installation of some productivity software. Microsoft Works 4.0 for Windows 95 needs dynamic CPU core (so nothing for OS4/MorphOS) and works without problems. I was even able to open my master thesis (moderately long - 130 pages - formated text with footnotes) in RTF. It is really sad that more than 15 years old application offers better features (MS Word compatibility, support for Czech language, footnotes) than any current text editor for Amiga.

@pavlor

"It is really sad that more than 15 years old application offers better features (MS Word compatibility,"

Blame M$.

_________________
- KimmoK
// For freedom, for honor, for AMIGA
//
// Thing that I should find more time for: CC64 - 64bit Community Computer?

@Thematic

What is your problem about C: ?

If there is no other comment, I will prepare a release in the coming days.

I ran the Doom benchmark :
- dosbox 0.74, original, on MacMini G4 Linux : 7548 realticks, 9.9 fps
- dosbox 0.74, modified, on MacMini G4 Linux : 6726 realticks, 11.1 fps
- dosbox 0.74 original, on MicroAOne G3 OS4 : 9730 realticks, 7.7 fps
- dosbox 0.74 modified, on MicroAOne G3 OS4 : 8379 realticks, 8.7 fps

So globally, that is an improvement on about 12-13 %.

I can't do more. I again ran a session of profiling and new changes did nothing and more, I am never sure that won't cause a regression on another CPU. I spent enough time on that for no more improvement.

Edit :
- dosbox 0.74, original, on Sam440/667 Linux : 33806 realticks, 2.2 fps
- dosbox 0.74, modified, on Sam440/667 Linux : 30967 realticks, 3.5 fps

Last edited by corto on 09-Aug-2011 at 02:39 PM.

@corto

I have a QWERTY-keyboard, PS/2.
The keyboard doesn't respond properly, with my dosbox.conf from last year. If I remove this file, it doesn't work at all, but I'll describe the somewhat working case: I get letters and apparently the colon (':') by pressing shift and the key right from M. Most of the characters you'd expect to enter with the shift qualifier don't come up and some keys are dead. For example two keys right from L don't do anything.

I haven't determined if applications and games (and how many of them) demonstrate similar behaviour.

_________________
: AmigaOneXE (unmod.) 750FX/512 MB +stuff & AmigaOS 4.(0|1)
: A1200/68060&96MB/SCSI/EM1200-Voodoo3 & OS 3.5
: A500/1MB
: Pegasos (ff) 512 MB & MorphOS
Praise seitan.

@corto

Quote:

I can't do more.

You did wonderful work!

My 486SX 25 MHz scores 9.9 FPS (without sound), your results are really good. Better than 386DX performance is fully sufficient for most good old games.

my great oldest 486SX33 with TsengLab ET4000/32 Vesa loca bus built in, with Doom and Doom2 take 35 fps.. ( DOS)

_________________

@Seiya

Quote:

my great oldest 486SX33 with TsengLab ET4000/32 Vesa loca bus built in, with Doom and Doom2 take 35 fps.. ( DOS)

I fear you must use other Doom port than rest of us.

My 486SX 25 MHz with plain VGA reaches only 9.9 FPS. According to the Doom benchmark page 35 FPS is equal rougly to 486DX/2 80 MHz with VLB GFX card. Shareware Doom from ID Software must be used to get comparable results.