On Sun, Oct 29, 2017 at 9:20 PM, Steve Nickolas <usots...@buric.co> wrote:
> On Sun, 29 Oct 2017, Jim Hall wrote:
>
>> That said, I'd love to see other tools become part of FreeDOS. If
>> there was a DOS-native GCC that could generate 16-bit binaries in the
>> different memory models, I'm all for that.
>>
>
> And that's probably the gotcha. Is GCC even capable of handling all those
> models? Though to be fair, it *might* (apart from the weirdness of having
> the segment shifted like it is) be able to handle the large or huge model,
> and isn't the medium model the classic "split i/d" of early Unices?
>
The answer is no to memory models but I'm guessing a yes to DOS-native
GCC. Chris Wellons/skeeto/nullprogram wrote a game and a blog [0] and
published a github repo [1] demonstrating how to call DOS to print [2] and
use ld [3][4] to link a 16-bit/32-bit COM file (32-bit is really prefixed
32-bit instructions). Things that would be familiar to old ASM devs or C
devs comfortable with inline ASM. While he uses the -m32 flag, nothing
I've seen should prevent the usage of -m16.
[0] http://nullprogram.com/blog/2014/12/09/
[1] https://github.com/skeeto/dosdefender-ld31/
[2] https://github.com/skeeto/dosdefender-ld31/blob/master/print.h
[3] https://github.com/skeeto/dosdefender-ld31/blob/master/Makefile
[4] https://github.com/skeeto/dosdefender-ld31/blob/master/com.ld
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
