You mean not having a size restriction for inlining methods or Mono.Simd? Well, I pretty much hate the idea of having such special casing in the jit. It won't make stuff work better and will increase the amount of voodoo inside the JIT, which is bad.
And, besides that, inlining the code in Mono.Simd won't cut unless the JIT implements a value-scalar replacement optimization to decompose vtype members into regular scalar ops. What would be useful would be JIT hinting to force inlining. This would be more broad and useful. This has been discussed before and had a general agreement that would be useful. Feel free to implement both optimizations, I'll gladly review them. Cheers, Rodrigo On Fri, Jan 16, 2009 at 8:55 PM, crashfourit <[email protected]> wrote: > > I was wondering what would people here think about ignoring the > "inline_limit_inited" on line 3332 in method_to_ir.c for a few specific > cases: Operator overloads, getters and setters, and the methods in Vector4f > when they are not being accelerated. >
_______________________________________________ Mono-devel-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-devel-list
