[Mono-dev] Ping on nternal call builders

Kornél Pál kornelpal at gmail.com
Wed Jul 30 06:18:09 EDT 2008


>Massimiliano Mantione wrote:
> The good news is that the current commit of the linear IR work
> is the first step in getting a better JIT infrastructure so
> that we can handle these things properly.

Thanks for the explanation about inlining. Now I understand that it's 
even more complicated than I thought. Anyway I think that it's better to 
let the JIT decide whether to inline managed-to-managed wrappers instead 
of forcing to inline them always.

I succeeded with the new IR. The old IR has more checks so it's not 
worth to patch it.

I have attached the new patch and a new test for OffsetToStringData.

I got results around 59900 with and without the patch as well.

Note that inlining constructors is not covered by the patch but string 
.ctors would not be inlined because they call CreateString methods.

UnsafeAddrOfPinnedArrayElement will not be inlined either because 
[SuppressUnmanagedCodeSecurity ()].

OffsetToStringData is inlined for sure because without inlining I got 
results around 201100.

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ICallBuilderPerfTest2.cs
Url: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20080730/e2132504/attachment-0001.pl 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: icall_builder_new_ir.diff.txt
Url: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20080730/e2132504/attachment-0001.txt 

More information about the Mono-devel-list mailing list