On 2/27/09, Jb Evain <[email protected]> wrote: > The issue is the pop, in between the ret and the jump target. .net's > JIT will optimize it away, and not even verify it, as it will never be > executed.
It's definitely a common pattern: push condition brfalse target ldarg 3 // action on the RubyContext ret pop target: bla bla bla I guess it shouldn't be too hard for you guys to bisect where the issues comes from between 10606:12221. -- Jb Evain <[email protected]> _______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
