[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

> Thank you.  The POD is a little thick, and I'll be printing it out so I can
> follow along.  I'm going to copy the i386 path to an a64 path and have at it.
> I'm hoping it won't be much of a stretch to get 64-bit code generated --
> although REASONABLE 64-bit code is another problem.  But first I want
> to ask if
> anybody else is doing this already.

Yep.

> ... I don't know what I'm getting
> myself into,
> other than at least modifying ~5,000 lines of code.

The biggest problem with jit/i386/jit_emit.h is that there are two
layers above one another: old code C<emit_*> and the newer and more
regular C<jit_emit_*> as described in the naming conventions for JIT
code. And to complicate matters and bewilder a casual hacker operand
directions are reversed between the two layers.

It's probably best to start over with a cleaner implementation that
additionally has a notion of the REXX prefix for x86-64. I don't know
anything about license issues, but:

  $SRC/mono-1.x.y/mono/arch/amd64/amd64-codegen.h

might be a better start.

leo

Reply via email to