19-Янв-2007 15:09 [EMAIL PROTECTED] (Japheth) wrote to

>>      May you show examples? Starting from minimal "void main(){}", then with
>> printf("Hello, world!\n"), then something more complex? With OW 1.6:
J> a "dummy" main and a "hello world" main are utterly irrelevant if you want to
J> compare size/speed optimisations (leaving CRT aside).

     For applications, RTL usually is inherent part, so comparing RTLs
(which also compiled by compilers) together _is_ relevant. On the other
side, given examples make bias point - you may now enough to bias executable
size and compare resulting sizes, not instructions versus instructions.

J> A "complex" sample is Jemm386 C part (it can be compiled with both MSVC and
J> OW). It is still small model, but uses some far pointers, and OW is very dump
J> with far pointers.

     How much?

>      ?! Using 32-bit instructions in 16-bit programs may be useful, but this
> is another story. How this relates to difference in generating 16-bit code?
J> if this is another story, then why does a program benefit both in size and
J> speed if you add the -G3 switch ("use 80386 instructions") in MSVC 1.5?

     I mean, that generating 32-bit instructions for 16-bit programs is
another story. Of course, its pity, that OW/16 doesn't reuses 32-bit
instructions (interesting, OW/32 may generate 16-bit code?), but what about
comparing 16-bit code generators?

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
Freedos-user mailing list

Reply via email to