> On Jun 2, 2026, at 1:58 PM, Rugxulo via Freedos-devel > <[email protected]> wrote: > > Hi, > >> On Mon, Jun 1, 2026 at 10:14 AM Jim Hall via Freedos-devel >> <[email protected]> wrote: >> >> Mathias Eberle on the Facebook group shared this announcement, which I >> am re-sharing here: >> >>> I fulfilled myself a little 90s childhood dream and created a single-pass >>> self-compiling BASIC compiler for DOS, targetting 8086/8088 and size >>> optimized COM files as output! >>> >>> The compiler itself generates NASM-compatible code. But since NASM >>> usually generates 386+ code, I have also included a special assembler >>> written in BASIC, so that the toolchain is complete. > > This sounds very cool, but I haven't tried it yet. > > Not sure what he means about NASM. I guess he means the default > binaries for modern NASM require 386 (and DPMI) from DJGPP. > > If his code doesn't require modern NASM preprocessor tricks, if it can > assemble with old 0.98.39 (from 2005), then we have 8086 builds of > that version (TurboC or OpenWatcom). >
While I do not recall the default CPU target, NASM does not “usually” generate such code. This is because it is always a good practice to tell NASM your target with a keyword in the source file. Then you get a binary compatible which the processor you want to target. No different than specifying the offset of the code for things like COM files by using “org 0x100” So, that statement about it usually generates 386+ code makes no sense to me. Unless, the statement is in regards to running NASM. Then because NASM is huge, you would be limited to compiling using a 386+. > > _______________________________________________ > Freedos-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freedos-devel _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
