> Badly written ifdef in memdisk.asm. Fixed such that 486+ compiles.  Read (
> ftp://openwatcom.mirrors.pair.com/manuals/current/cguide.pdf) and sections
> 2.3.x & 3.5.  Enlightening and disappointing.  There does not seem to be a
> way to get 32-bit instructions out of wcc as Tom had mentioned.  3.5
> recommends
Watcom is open source; feel free to add 32 bit instructions to the 16
bit compiler

> "The recommended options for generating the fastest 16-bit Intel code are:
> Pentium Pro /onatx /oh /oi+ /ei /zp8 /6 /fpi87 /fp6
> Pentium /onatx /oh /oi+ /ei /zp8 /5 /fpi87 /fp5
> 486 /onatx /oh /oi+ /ei /zp8 /4 /fpi87 /fp3
> 386 /onatx /oh /oi+ /ei /zp8 /3 /fpi87 /fp3
> 286 /onatx /oh /oi+ /ei /zp8 /2 /fpi87 /fp2
> 186 /onatx /oh /oi+ /ei /zp8 /1 /fpi87
> 8086 /onatx /oh /oi+ /ei /zp8 /0 /fpi87"

> -ot of -onatx & -zp8 contradict the original makefile's code -os & -zp1
> (optimize execution time vs. executable size & align on byte vs. 8-byte,
> respectively).  Also, the -fp*'s opts don't apply and wcc barfs on -oi+.

we *want* -os  (optimize for size); size matters. both size on disk and
size in memory are (somewhat) important. speed does *not* matter as
there is virtually no time spend *inside* the kernel.

to experiment, run some benchmark (like compiling a big project), on
an optimized kernel vs. not optimized kernel vs. borland kernel.
measure times. think.

we *need* -zp1 as DOS structures have specific byte offsets.


Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
Freedos-user mailing list

Reply via email to