diff options
author | Miguel de Icaza <miguel@gnome.org> | 2002-04-22 00:34:17 +0400 |
---|---|---|
committer | Miguel de Icaza <miguel@gnome.org> | 2002-04-22 00:34:17 +0400 |
commit | d7bfce6071b0e318c2bb04cb88b198eda97335b4 (patch) | |
tree | b108c64ab579ce3b13e1853b02434bceac1cb58e /web/runtime | |
parent | dc666c66f2f8552becb6a56807e65b14a59e0b16 (diff) |
Flush
svn path=/trunk/mono/; revision=3944
Diffstat (limited to 'web/runtime')
-rw-r--r-- | web/runtime | 28 |
1 files changed, 22 insertions, 6 deletions
diff --git a/web/runtime b/web/runtime index 981e2a8d88c..908600e8f84 100644 --- a/web/runtime +++ b/web/runtime @@ -19,11 +19,6 @@ Currently we are using the Bohem conservative garbage collector, but we working on incorporating the ORP GC engine. -* COM and XPCOM - - We plan on adding support for XPCOM on Unix and COM on Microsoft - Windows later in our development process. - ** Executing MSIL/CIL images The code will load an executable and map the references to @@ -64,13 +59,29 @@ Unix-like compilation environment (mostly we use GNU make in a few of the makefiles). -** JIT Engine (<b>updated, March 26th, 2002</b>) +** JIT Engine (<b>updated, April 21, 2002</b>) The JIT engine uses a code-generator generator approach for compilation. Given the properties of CIL byte codes, we can take full advantage of a real instruction selector for our code generator. + The JIT engine implements a number of optimizations: + + <ul> + * Opcode cost estimates (our architecture allows + us to generate different code paths depending + on the target CPU dynamically). + + * Inlining. + + * Constant folding. + + Although compilers typically do + constant folding, the combination of inlining with + constant folding gives some very good results. + </ul> + There are a couple of books that deal with this technique: "A Retargetable C Compiler" and "Advanced Compiler Design and Implementation" are good references. You can also get a @@ -177,3 +188,8 @@ href="archive/mono-tests.tar.gz">Mono regression test suite</a> useful to debug your implementation. +* COM and XPCOM + + We plan on adding support for XPCOM on Unix and COM on Microsoft + Windows later in our development process. + |