Re: New back end ia16: 16-bit Intel x86

[rridge@csclub.uwaterloo.ca (Ross Ridge)]

Ross Ridge wrote:
> I have 16-bit C code, that when compiled with my 16 year-old Borland
> C++ compiler, produces code that uses 32-bit registers and instructions.

Rask Ingemann Lambertsen writes:
>   Why cant the latter group do what the Linux kernel does? That is, use
>i386 gcc and i386 binutils for low-level 16-bit system code targetting an
>i386 or better.

I can't speak for anyone but myself, but I don't use hacks like
".code16gcc" or code everything assembly because I've got a fully
functional 16-bit IA-32 C compiler that I can use instead.  It would be
nice to use GCC entirely in my projects but I'm not going to replace a
working tool with a broken one to do so.

Let me ask you question.  Are you serious about this port?  Is it just a
toy, a fun project to work on, or do you expect to be used for serious
development?  Who do you expect to use the port?  If you're serious
about this port then you shouldn't be asking why people can't the same
hacks the Linux kernel does, but instead if your port couldn't be used
one day with Linux kernel.

On the other hand, if it's ment to be little more than a toy then you
can just ignore everything I've said.  The name "ia16" is still wrong,
but if it's just going to become, at best, a little-used embedded target,
I really don't care what you call it.

					Ross Ridge