Hi,

I did some comparison regarding the speed of generated code for several C compilers, namely IA16-GCC, Open Watcom 2 BETA 1 (the "original" from openwatcom.org) and Turbo C++ 1.01.

I used my "computation heavy" sha3sum [1] utility to time how long it takes to calculate the SHA3 sum of the FreeDOS 1.4 live CD KERNEL.SYS. The results are for DosBox running at 3000 cycles/ms (measured by stopwatch so somewhat inaccurate):

SHA3-256 sum: sha3sum -a 256 kernel.sys

IA16-GCC: ~ 5sec
Watcom: ~8sec
Turbo C++: ~9.5sec

SHA3-512 sum: sha3sum -a 512 kernel.sys

IA16-GCC: ~ 9sec
Watcom: ~15sec
Turbo C++: ~17.5sec

The compiler flags were:

IA16-GCC: -mcmodel=small -mnewlib-nano-stdio -mtune=i8088 -Os
Watcom: -ox -ms
Turbo C++: -G

Binary sizes:

IA16-GCC: 19728 bytes
Watcom: 20544 bytes
Turbo C++: 17510 bytes

The speed advantage of the IA16-GCC built executable is quite impressive in this case. Just wanted to let you know...

Here the SHA3 sums for completeness:

SHA3-256:
915edcdc5ed00793ecd3d12737d5d51f8bcfb88cf08cd940b4075b0ca1c04d1a

SHA3-512:
2d19fc2c1ebec609c23a8ae92bd2a221956eb2c2f9b549b86a2105ecb01bbd84f31fd072adc292dac6ffb90d2092da4dc2ad31df32bbf51515338e9d27ce4bec

Greetings, Bernd

[1] https://codeberg.org/boeckmann/sha3sum




_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to