Re: 80386 C compiler

On 24/11/2024 17:51, fir wrote:

Paul Edwards pisze:

Hi.
>
I have been after a public domain C compiler for decades.
None of them reach C90 compliance. SubC comes the
closest but was written without full use of C90, which
makes it difficult to read. I'm after C90 written in C90.
>
A number of people have tried, but they always seem
to fall short. One of those attempts is pdcc. The
preprocessor was done, but the attempt (by someone
else) to add C code generation was abandoned.
>
I decided to take a look at it, and it looks to me like
a significant amount of work has already been done.
>
Also, my scope is limited - I am only after enough
functionality to get my 80386 OS (PDOS) compiled,
and I don't mind short=int=long = 32 bits, I don't
mind not having float. I don't use bitfields.
>
Anyway, I have had some success in making enhancements
to it, and here is one:
>
https://sourceforge.net/p/pdos/gitcode/ci/3356e623785e2c2e16c28c5bf8737e72df
d39e04/
>
But I don't really know what I'm doing (I do know some
of the theory - but this is a particular design).
>
E.g. now that I have managed to get a variable passed to
a function, I now want the address of that variable passed
to the function - ie I want to do &x instead of x - and I am
not sure whether to create a new ADDRESS type, or
whether it is part of VARREF or what - in the original
(incomplete) concept. Or CC_EXPR_AMPERSAND.
>
I am happy to do the actual coding work - I'm just looking
for some nudges in the right direction if anyone can assist.
>
Thanks. Paul.
>
>

you mean there is no such a compiler? rise a fund for some to
write it and they will write it..and if few thousand of people
will give some money there it will be written

There are any number of open source C compilers. But they need to be good enough (too many support only a subset, which may not be enough for the OP) and they need to be public domain for the OP's purposes.