Sergey Tikhonov wrote:
Jonathan Pryor wrote:
On Fri, 2006-01-20 at 20:27 +0300, Sergey Tikhonov wrote:
Well, it it really pity since it seem that even this "unsupported"
interpretator does a lot of work and give chance other arches
to try Mono. :) Ok, I will see if I could find what the problem is....
The problem is that it's impossible to have a 100% portable interpreter,
because of internal calls and P/Invoke. Both of these invoke native
code, either within the runtime itself or within a shared library, and
this requires processor-specific code to place parameters in the correct
registers, etc.
Since processor-specific code is required *anyway*, it was considered
reasonable to just require the JIT for most uses, since (afaik) the JIT
doesn't require _much_ more custom code than the marshaling code already
required...
Ok, I just thought that the problem I have is somewhat simple. Anyway,
I think I found the way
how to track it down (so far it fails in ctor of System.Decimal and
based on interpreter trace the
ctor is called with some bogus params).
Ok, after some debugging - it seems that interpreter works correctly
with mscorlib.dll from "monolite"
class/lib directory, but fails with newly built mscorlib.dll. Any way I
hit to "unsupported" feature...
Any links/hints what is required to create JIT? I looked through the
site and didn't find any usefull info...
Only source code is the documentation?
Thank you,
--
Sergey Tikhonov
Solvo Ltd.
[EMAIL PROTECTED]
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
