Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

OMF records (Developers)

posted by Rugxulo Homepage, Usono, 18.02.2012, 17:32
(edited by Rugxulo on 18.02.2012, 17:42)

> > Two's compliment, ASCII, little endian, 32-bit regs, 8-bit bytes, flat
> > memory model, FPU always present, [un]aligned memory access, Unicode,
> > threads, garbage collection, LFNs, POSIX support ... how many more
> > assumptions can we make without looking foolish??
>
> Till somebody either supports otherwise, or pays people to do.
>
> Apparently nobody was ever interested in a truly free 16-bit linker. Since
> then they would have written one.

BCC/Dev86's LD86 (a.out variant) doesn't count? But I digress ... nobody in "modern" Linux, *BSD, or Windows cares about 16-bit, so they don't use it.

There are plenty of freeware or free/libre linkers for DOS (ALINK, VALX, WLINK), but, as mentioned, we're dealing with various somewhat incompatible variants: Intel, MS, Borland, TIS, etc. The 32-bit extensions (from MS, Borland, others??) to OMF came much later than the original format and seem to be less widely supported in some cases. As mentioned, OpenWatcom uses OMF for various obscure reasons (mostly historic), e.g. even on Win32 (though not Linux, obviously), similar to older Borland Win32 stuff. But obviously MS uses PE/COFF, DJGPP uses "plain" COFF, AIX uses XCOFF, Ultrix and Tru64 (and VMS?) used ECOFF, Mac OS X uses Mach-O, *BSD used to use a.outb, etc. etc. etc.

There are several other Oberon compilers, see my other (Wirth birthday) thread, mostly all 32-bit, so I don't "need" Oberon/M, just messing around with it because it's tiny and seems to work fairly well for what it does.

 

Complete thread:

Back to the forum
Board view  Mix view
22762 Postings in 2122 Threads, 402 registered users (2 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum