gnupic@linuxhacker.org

On Tue, 29 Feb 2000, Matthew Bowles wrote:

> If you can go this far without to much trouble, perhaps it is becoming a
> small step for gpsim to accept .asm files. i know there's more to
> compiling than converting mnemonics to opcodes, but if you can do that..
> well maybe there's a gpsim.0.19 w/ assembler.

I don't think so... It's one thing to decode an instruction, but an
entirely different thing to implement an assembler. I'd spawn gpasm before
writing a gpsim assembler. What I was thinking about instead was to accept
one assembly instruction at a time. I couldn't read a raw assembly file
(unless it was formatted perfectly) because often times there are forward
references. (gpasm is a two-pass assembler - on the first pass, all of the
forward references are resolved and on the second the code is generated).

I doubt that this feature will appear in gpsim-0.19.0. There's a whole lot
of infrastructure that would have to be created to support it. (But
perhaps creating a one-line assembly program and spawning it off to gpasm
wouldn't be a bad idea...) I only mentioned it to throw out some ideas and
stimulate some discussions like these.

Scott