Brent --
> # My first cut is pretty sloppy, but it does generate this C file, which
> # compiles, but I don't have the time to figure out how to get
> # it all the
> # stuff it needs to link to. If someones gets it running, I'd
>
> Parrot::Config may come in handy, especially @PConfig{qw(cc ccflags
> libs)}.
I've had to comment out PConfig-related code from assembler.pl and
disassembler.pl lately, so I dont' think I want to muck with it
until all that stuff is working.
There are lots of things about this code that need improvement, since
I created it by forking disassembler.pl (Simon has already pointed out
some infelicities there, such as hard-coded pack templates) and
process_opfunc.pl (Major hackage here; I figured out only enough about
it to mutate it into something that seemed to do a decent job of
grabbing sections of code into an op-mnemonic-keyed hash).
> I modified my Makefile:
> [munch]
BTW, beware of targets that would be named 'test' on *nix, since *nix
has a 'test' program that is likely to be in the path.
> and it built, but gave me a GPF (from trying to read memory at 0x4) when
> I ran the resulting program. Make sure that you delete test$(O) before
> trying this--it's a remnant from the Configure process I never thought
> of. I'll patch Configure to delete it soon.
Chances are good that you were at least having trouble do to the string
constants not being loaded into the interpreter (I pointed this problem
out a few minutes ago in a related message). Perhaps getting those
string-constant-loading statements in there as directed earlier would
solve this problem (but no guarantees -- I wrote this code under a major
time crunch, more to prove it was possible than anything else).
Thanks for taking a look at it, and good luck if you work with it more...
Regards,
-- Gregor
