🚀 go-pugleaf

A few questions (gcc-2.5.8):

1.  What is "bytecode"?  Is there a document describing it?

1a.  Can anyone compile with -fbytecode successfully?  On what kind of
system?

I compiled a incarnation of gcc hosted on sparc (sunos 4.1) with the
m68k (m68k-sun-sunos4) as a target (the only architecture that
supports bytecode) but cc1 coredumps before generating any output.

For the heck of it, I sucked the bytecode stuff from m68k.h into
sparc.h (yeah, I know the output won't be usable -- I'm still trying
to figure out what the output -is-) and I get a SIGSEGV from that cc1.

2.  Has anyone modified GCC to dump the parser's output, i.e. what gets
passed to `rest_of_compilation', or `rest_of_decl_compilation' in
`toplev.c'?

I'm working on some ideas where I need to parse a C program into a
form where I can analyse it with another program.

Send replies to me; if I get answers and there's interest, I'll post a
summary.

Glen Overby <overby@cray.com>