> I tried to ran cc2 from the directory, but it still hangs.
> Even if I simply try "./cc2". The same applies to
> cc2-amd64-sysv and cc2-i386-sysv.
yes, it is logical because cc2 reads the input data from stdin, so if
you execute it without piping into it the output of cc1 then it will
wait forev
Louis Santillan wrote:
The C version of Let's Build a Compiler is here [0][1]. There are
multiple versions/recent updates by people other than Peter Gray's
original translation [2][3][4]. The original/Pascal version by Jack
Crenshaw is here [5]. I've also been reading Wirth's original Pascal
c
The C version of Let's Build a Compiler is here [0][1]. There are
multiple versions/recent updates by people other than Peter Gray's
original translation [2][3][4]. The original/Pascal version by Jack
Crenshaw is here [5]. I've also been reading Wirth's original Pascal
compiler writing books & w
> I think compilers are way over my level, but it's a subject that interest me
> and
> clang is massive c++, gcc is nonstandard bloat, tcc doesnt seem sufficient,
> so I wanna help.
There are a lot of places were helping without having a big idea about
compilers. The scc driver is one of the pl
k...@shike2.com wrote:
[...]
Thanks for the info! I ran "make multi; make install", however...
The error that should not happen is the error related to cc2. Do you
have it in $PREFIX/libexec/scc/?
I tried to ran cc2 from the directory, but it still hangs.
Even if I simply try "./cc2". The s
> Yes, it is in a very early stage. Cc1 is really advanced, and it can
> parse and generate intermediate code for almost all C90, and about a
> 90% of C99. Cc2 is only a draft. I had an advanced version of cc2
> for z80, but I discarded it and I began from the beginning with the
> idea of having
