diff options
| author | Miguel de Icaza <miguel@gnome.org> | 2002-03-26 23:20:57 +0300 |
|---|---|---|
| committer | Miguel de Icaza <miguel@gnome.org> | 2002-03-26 23:20:57 +0300 |
| commit | 0ec37d4c9effafb0293409cacb9a24cceae83a85 (patch) | |
| tree | e9d591e28cd0a392056179fd177fb97d1ecba54c /web/runtime | |
| parent | c47a50c75ce35c8282612442ab0eed33313fe737 (diff) | |
Update
svn path=/trunk/mono/; revision=3374
Diffstat (limited to 'web/runtime')
| -rw-r--r-- | web/runtime | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/web/runtime b/web/runtime index 0bd5ebc83a6..e5da8abc274 100644 --- a/web/runtime +++ b/web/runtime @@ -65,7 +65,7 @@ Unix-like compilation environment (mostly we use GNU make in a few of the makefiles). -** JIT Engine (<b>updated, Dec 18th, 2001</b>) +** JIT Engine (<b>updated, March 26th, 2002</b>) The JIT engine uses a code-generator generator approach for compilation. Given the properties of CIL byte codes, we can @@ -88,8 +88,22 @@ </ul> +** Future plans + + We are evaluating the future directions for the JIT engine: + both from our needs (optimizations like inlining, better register allocation, + instruction scheduling, and porting to other CPUs). + + We have not yet decided how we will evolve the JIT engine. We + might just upgrade our current architecture, and provide optimizations as + an extra layer. + ** Garbage Collection + Currently we are using the Boehm conservative GC. Although our plans + are to move to the Intel ORP GC engine, our plans on a next generation + dual-JIT engine have to be taken into account. + We will be using the Intel ORP GC engine as it provides a precise garbage collector engine, similar to what is available on the .NET environment. |