> If you look at the IL code, it's completely stack based. You push on > values, pop values off, different operations do different things to > the stack, etc... why not translate the IL into simple x86 stack > operations?
Actually that's what we are doing with IL2CPU now, and then we are making optimizers pluggable. We need something that is modular, easy to work on, and flexible. > in C#, the IL pushes that value onto the "IL stack". Why not simply > translate that into an x86 push operation? In fact, almost all IL > commands can easily be translated to simple x86 operations. The only In fact that's the goal behind IL so it could be JITted fast. > Chriss's AOT compiler does a lot more than my simple compiler would > (mostly dealing with optimizations). If I had more time I'd love to > test out my idea though. Yes. Ive been talking with Chriss a lot. I realize it does a lot. But its grown quite complex internally, and that's why Im building a prototype to discuss some ideas for reform. But whats in AOT is very valuable and reusable should we decide to use the prototype further. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
