[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] CFront for TinyCC?

From: Domingo Alvarez Duarte
Subject: Re: [Tinycc-devel] CFront for TinyCC?
Date: Thu, 4 Nov 2021 13:49:52 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0

Hello Christian !

As you said it's for "historical research purposes only" and for fun.

I could get it to compile and bootstrap on Linux 32/64 bits, Windows 32/64 bits cross compiling with mingw64 and wine and also OSX the output of all of then can be viewed here https://github.com/mingodad/cfront-3/actions/runs/1421141006 .

And some pending issues here https://github.com/mingodad/cfront-3/issues .

Again any comments/suggestion/pull requests are welcome !

Cheers !

On 2/11/21 14:51, Christian Jullien wrote:
Hi Domingo,
This is very interesting but I wonder what it will be used for?

Stroustrup and others explicitly say that CFront should not be used for any 
purpose except for historical research purpose:

"The source code in this section is posted with the permission of the copyright 
owner for historical research purposes only."

It's fine if you use it within this scope otherwise you should not promote this dev. as a 
way to have a "kind of" C++ on top of tcc.


-----Original Message-----
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange.fr@nongnu.org] On 
Behalf Of Domingo Alvarez Duarte
Sent: Tuesday, November 02, 2021 14:07
To: tinycc-devel@nongnu.org
Subject: [Tinycc-devel] CFront for TinyCC?

Hello !

After making tinycc fully reentrant here
https://github.com/mingodad/tinycc I decided to have a look at cfront
and after a week of work on a fork from seiko2 I've got it to build for
32/64 bits for linux here https://github.com/mingodad/cfront-3 , it also
build on OSX and MYSYS2 with a bit of dirty tweaking that I need to
figure out how to clean up.

I also fixed the parser to build with bison but the generated parser
doesn't work as expected, need more investigation because bison doesn't
find the same conflicts as byacc in a few places.

I already read the prior messages and understand the implications of the
license, but for research and history preservation I think it was worth
the trouble so far.

It can build itself through valgrind without any invalid memory access
(of course it leaks memory as usual for this kind of software and it's

If anyone want/can give it a try and give any feedback I appreciate and
thank you in advance !

Cheers !

Tinycc-devel mailing list

Tinycc-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]