Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| On-the-fly compilation from VM code to machine code joe@erix.ericsson.se (1994-08-24) |
| Re: On-the-fly compilation from VM code to machine code thomasl@groucho.csd.uu.se (1994-08-26) |
| Re: On-the-fly compilation from VM code to machine code danhicks@aol.com (1994-08-27) |
| Re: On-the-fly compilation from VM code to machine code hbaker@netcom.com (1994-09-07) |
| Re: On-the-fly compilation from VM code to machine code engler@AMSTERDAM.LCS.MIT.EDU (1994-09-07) |
| Re: On-the-fly compilation from VM code to machine code hoelzle@xenon.stanford.edu (1994-09-14) |
| Re: On-the-fly compilation from VM code to machine code danhicks@aol.com (1994-09-09) |
| Re: On-the-fly compilation from VM code to machine code pardo@cs.washington.edu (1994-09-16) |
| Newsgroups: | comp.compilers |
| From: | hbaker@netcom.com (Henry G. Baker) |
| Keywords: | interpreter, optimize |
| Organization: | nil |
| References: | 94-08-151 94-08-164 |
| Date: | Wed, 7 Sep 1994 03:00:17 GMT |
>[re compiling on the fly to RISC code]
>The problem with this is that you can't optimize RISC code "on the fly".
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>The efficiency of the code generated would be little better than what you
>could do with an interpreter.
On the contrary, compilation 'on-the-fly' offers optimizations not
possible with static compilation. For example, instead of compiling for
every possible case, you need only compile for the cases that actually
occur, with traps for the cases not compiled for. For languages -- e.g.,
assembly languages -- in which types may be very dynamic, this use of
context can help a lot. Craig Chambers at the U. of Washington has been
doing this for quite some time with SELF, and this tradition goes back at
least to Peter Deutsch's Smalltalk compilers.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.