On 12/26/07, Bruce Markham <[EMAIL PROTECTED]> wrote: > [snip] Why is everyone so adamant about JIT compiling code? If you notice, Microsoft themselves tends to AOT compile assemblies (see SQL Server 2005 Manager). My original plan when I started this project was to AOT everything. When a user downloads a library / application, it comes in an IL assembly. The first thing the operating system does it AOT compile it.
So, yes, in my model, init is AOT compiled as EIC, and the kernel and mscorlib and AOT compiled as EDC. If you ignore features such as reflection, exception handling, and a few others, the only thing a running .net assembly needs is a stack and a heap. The stack stores both the values of structs (which includes the primitive types), and pointers to instances of classes. The actual instance of the class is stored on the heap. So, if I have this C# code: int i = 5; object o = new Object(); The stack will contain both the Int32 value 5, and a pointer to the object class. The heap contains the actual object class, which is empty. For each object on the heap, we need to store the number of pointers to it, so the garbage collector can do it's job. Haven't figured out the best way to do that yet. Anyway, I'm going to attempt to write a simple AOT, just something that does exactly what I need. Hopefully I can have a prototype of what I'm trying to do and we can see if it's a viable course. Johann ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
