(Resending, with git link instead of the source I attached, put me over the 40k limit...)
A couple of months back I hit JIT errors when using LINQ for objects. I was never able to resolve them, but as the LINQ involved was pretty simple, I just "unrolled" it into procedural code. Now I'm getting more of them, and I'd really prefer to leave the LINQ alone if possible. The exception I'm getting today is: Attempting to JIT compile method 'System.Linq.Enumerable:<ToLookup`2>m__18<JIT20110908.ActualScore, int> (JIT20110908.ActualScore)' while running with --aot-only. Below is my ProblemLinq.cs file, which contains a class with an Execute() method that causes this error. I realize there's a lot of interfaces and classes here; this is a severely dumbed-down version of the actual code, which is part of a cross-platform reporting library. The code in question is running in Windows as part of a production product. I've read the "Limitations" section on the xamarin website, and while I can't say I understand it totally, I don't see that my code is doing any of the verboten virtualization things; although LINQ does enough magic that I don't necessarily know the secondary effects of the code. The stack trace from the error this class causes follows the code. I'm running MT 4.0.7 and MD2.6. Am I doing some LINQ thing I shouldn't? Or is MT missing something? Thanks. You can find the source and my stack trace at: git://github.com/bschuth/MT-JIT-Problem.git -- Brian Schuth ALPHCE, Inc. Eastport, ME +1 207 370 2430 [email protected] -- Brian Schuth ALPHCE, Inc. Eastport, ME +1 207 370 2430 [email protected]
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
