[IronPython] what does MethodImplOptions.NoOptimization do?

Dino Viehland dinov at microsoft.com
Wed Sep 23 13:41:54 PDT 2009

It’s going to disable JIT optimizations on the individual method.  This was added because we were seeing some differences between release builds and debug builds around floating point math.   We need to track down the real issue but it may just be a CLR bug that doesn’t affect Mono (or maybe it’s a valid optimization that only shows up because floating point numbers aren’t being spilled from their 80-bit internal representation into memory as 64-bit values).

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Ivan Porto Carrero
Sent: Wednesday, September 23, 2009 1:11 PM
To: Discussion of IronPython
Subject: [IronPython] what does MethodImplOptions.NoOptimization do?


I'm looking at building ironpython on mono to create an rc1 package when the windows one has been released.

in the mathc.cs file on line 383 there is this attribute:

Mono doesn't have that value in the MethodImplOptions there is a work-around. But it did prompt the question what does MethodImplOptions.NoOptimization do?

Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ironpython.com/pipermail/users-ironpython.com/attachments/20090923/359e79f9/attachment.htm>

More information about the Users mailing list