Hey all.
  I know it's a little (OK, a lot) early for this, but has anybody
considered writing support for parrot bytecode and the parrot object
format into GNU binutils?  
  If you don't use some features of the VM (specificly, PMC and String
registers, destroying push), it isn't that different from a normal
machine.  (Not nearly as different as the JVM, and you can target that
IIRC.)

  This would give us access to a sophisticated assembler and binutils
(objdump, ld), and would give the possiblity of porting gcc/g++, which
would be a Big Win. 

AFAICS, the biggest thing this requires from Parrot that it doesn't yet
have is constant opcode numbers.  This shouldn't be very hard to do.  It
does mean admitting that the opcode numbers won't be in a logical order,
but if we want to maintain bytecode backwords compatablity all the way
down, we're going to get there sooner or later (probably sooner).

        -=- James Mastros
-- 
Put bin Laden out like a bad cigar: http://www.fieler.com/terror
"You know what happens when you bomb Afghanastan?  Thats right, you knock
over the rubble."       -=- SLM

Reply via email to