Hi Sander, There's only two options available IMHO:
1. IL2CPU from Cosmos Which could be used, but has its fair share of issues too. I'm certain that we could get further with it than the AOT, but we still can't do an advanced design AFAIK, as there's no support for Attributes, Reflection, ... However we would have to ask Matthjis about this. 2. Bartok We all know what that means ;) Ensemble doesn't have one, but Scott is contributing to the MOSA compiler and in total there's now 4-5 people working on it directly or indirectly. A prioritized list of features would allow us to drive the compiler into a specific direction, e.g. support certain things earlier than later. Ensemble is in the same position as SharpOS with this respect, except they don't even have an AOT to work with. Further speedups in the compiler are not possible right now, as there's some blocking points that need to be resolved before we go ahead and add more manpower to the compiler. I'm happy with those who contribute their time, code and mind to it. In fact I think we should use the time to redesign specific parts of the kernel and refactor the existing code base. I know its hard without writing a piece of new code, but I think this is the right time to document what we have, where we want to go and how we want to get there. Mike > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Im > Auftrag von Sander van Rossen > Gesendet: Dienstag, 5. August 2008 10:42 > An: sharpos-developers@lists.sourceforge.net > Betreff: Re: [SharpOS Developers] MOSA / AOT > > Yes, but the problem is that the AOT is missing some > functionality, or has some bugs, which prevent us in properly > implementing some parts of the kernel. > In a way, we're kinda stuck and can't go forward because of it. > So either we fix those bugs in the AOT, and implement those > features that we need (which would be hard because the > person(s) that know the most about the AOT are no longer > active), or we wait until the new MOSA compiler is mature and > developed enough to continue with the kernel. > > Just to throw in another option: > Don't the other teams, or at least the Cosmos, have compilers as well? > Although they're not designed as well in the basis as the > AOT, maybe we could 'borrow' one of these compilers for the > time being until the MOSA compiler is finished? > > > On Tue, Aug 5, 2008 at 9:45 AM, Zachary Gorden > <[EMAIL PROTECTED]> wrote: > > Even if the intention is to replace the AOT, there shouldn't be any > > reason to not continue development using it right now. The code > > should still compile with a new compiler. > > -------------------------------------------------------------- > ----------- > This SF.Net email is sponsored by the Moblin Your Move > Developer's challenge Build the coolest Linux based > applications with Moblin SDK & win great prizes Grand prize > is a trip for two to an Open Source event anywhere in the > world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > SharpOS-Developers mailing list > SharpOS-Developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sharpos-developers > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
