|INTERMEDIATE CODE DESIGN email@example.com (1995-06-24)|
|Intermediate code design firstname.lastname@example.org (David Stone 5887) (1998-01-05)|
|Re: Intermediate code design email@example.com (1998-01-06)|
|Re: Intermediate code design firstname.lastname@example.org (David Chase) (1998-01-06)|
|Re: Intermediate code design email@example.com (Charles Fiterman) (1998-01-08)|
|Re: Intermediate code design firstname.lastname@example.org (Christian von Roques) (1998-01-08)|
|From:||email@example.com (STEPHEN SURYAPUTRA)|
|Keywords:||C, design, question|
|Organization:||iCon BBS / Surabaya, Indonesia / (62) (31) 566-0625|
|Date:||Sat, 24 Jun 1995 12:11:55 GMT|
I'm currently writing a full ANSI C compiler, and I want to make the
compiler very portable and easy retargetable to different platform. I'm
interested in Jim Hendrix's Small C approach which use a table to
associate p-code and 8086 assembly string code. If the translation table
stored in a file, the user of the compiler can retarget the compiler
without rebuilding the compiler.
I want to use that approach, but Jim Hendrix's p-code cannot handle
variative data structure in ANSI C specification. And it seems that the
p-code designs to suit to Accumulator Based Machine (it has only 2
Does anyone know a different kind of p-code which is more general ? Any
suggestion regarding this is very welcome.
I appreciate any help and suggestion. Thank you.
Electrical Engineering Dept.
Sekolah Tinggi Teknik Surabaya
e-mail : firstname.lastname@example.org
Return to the
Search the comp.compilers archives again.