[vbox-dev] Unhappy with recent developments

Michael Thayer michael.thayer at oracle.com
Mon Dec 3 08:09:20 GMT 2012

Hello Pau,

On 02/12/12 20:55, Pau Garcia i Quiles wrote:
> On Tue, Nov 27, 2012 at 8:28 AM, Michael Thayer
> <michael.thayer at oracle.com <mailto:michael.thayer at oracle.com>> wrote:
>     To cut a long story short, Watcom was the free-est compiler
>     available which could generate decent 16-bit x86 code.  bcc was
>     always rather painful to use due to it's very limited support of
>     16-bit Intel memory models, and eventually the pain got too much.
> What would happen if some other compiler was used? Have you tried faucc?
> http://packages.debian.org/sid/faucc
> http://www3.informatik.uni-erlangen.de/Research/FAUmachine/
> Or is a C++ compiler required?
I had a quick look at what documentation I could find for faucc online, 
but I couldn't find any mention of memory model support, which is a 
requirement for us, as we don't want to jump through hoops to have more 
than 64K of BIOS code.  I may have missed this of course - do you have 
any more information?  (Note that I am not actually responsible for our 
BIOS code, I am just passing on what I know.)



More information about the vbox-dev mailing list