Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lynn McGuire <lynnmcguire5@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: 80386 C compiler
Date: Mon, 25 Nov 2024 15:55:09 -0600
Organization: A noiseless patient Spider
Lines: 49
Message-ID: <vi2rnt$31dba$1@dont-email.me>
References: <vhvbhf$28opb$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 25 Nov 2024 22:55:09 +0100 (CET)
Injection-Info: dont-email.me; posting-host="04735ac4ee0282c1472cbcf1424fe5a8";
	logging-data="3192170"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18JbzMDCt0pdr9Q5rrxuofPNvaR5OohG0c="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:AQORvfaDBtU4aKnraSLwEkFDguk=
In-Reply-To: <vhvbhf$28opb$1@dont-email.me>
Content-Language: en-US
Bytes: 2778

On 11/24/2024 8:00 AM, Paul Edwards wrote:
> 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.

Did you look at the Open Watcom compilers: C, C++, and F77 ?
    https://openwatcom.org/

Open Watcom has many modes of compilation: 8086, 80286, 80386, etc.

Lynn