Hello Rugxulo,

* 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/asm/nasm/0.98.39/8086host/

Though I wonder why I wasted so much time since it's inferior to the
8086 OpenWatcom build. I guess I still appreciate Turbo C++ for what
it is. I really need to take a look at why it's running out of memory

Sorry for the late reply!

Actually I will not be surprised, if the Open Watcom-compiled nasm was
simply more efficient memory-wise.  (At the very least, Open Watcom is
known to use a more efficient function call interface by default, so
there is that.)

Another possibility is that the Turbo C++ version was triggering some
memory corruption bugs which was causing spurious "out of memory"
errors.  Though I sure hope that was not the case.

(kernel.asm) or maybe even look into using overlays (which I'm not
familiar with at all). At least it does normally work, for comparison,
in case anyone wants to improve it.

(Me, I am not familiar with Turbo C++ overlays myself either --- perhaps
someone else on this list is.  I suspect that, to use overlays properly,
one will have to know a bit more about the general control flow of the
program, i.e. nasm, to guide the splitting of the program code.)

Thank you!

--
https://mastodon.social/@tkchia


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

Reply via email to