Related articles |
---|
Requirements for Just-in-time Compilation jp@demonseed.net (jason petrone) (2001-04-22) |
Re: Requirements for Just-in-time Compilation at150bogomips@aol.com (2001-04-26) |
Re: Requirements for Just-in-time Compilation ralph@inputplus.demon.co.uk (2001-04-26) |
Re: Requirements for Just-in-time Compilation vbdis@aol.com (2001-04-26) |
Re: Requirements for Just-in-time Compilation jp@demonseed.net (jason petrone) (2001-04-29) |
Re: Requirements for Just-in-time Compilation Brian.Inglis@SystematicSw.ab.ca (2001-04-30) |
From: | vbdis@aol.com (VBDis) |
Newsgroups: | comp.compilers |
Date: | 26 Apr 2001 21:14:35 -0400 |
Organization: | AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com |
References: | 01-04-120 |
Keywords: | incremental |
Posted-Date: | 26 Apr 2001 21:14:34 EDT |
jason petrone <jp@demonseed.net> schreibt:
>I've been reading papers and source code, but I still feel that I am
>lacking a clear understanding of the real issues involved in writing
>such a compiler.
Some issues:
- The compiler should run on the target system. This implies, that the
compiler is an executable program for the target platform.
- Above dictates, which constraints apply to the conversion of the
input code (OS, instruction set...).
- You didn't specify the nature of the input code. An emulator takes
any program, executable on a different platform, and executes it on
the actual platform. That's the worst case, where nothing else is
known about the input, besides that it's a native program for a
specific platform. If your object of interest is less
platform-dependent, you should specify...
DoDi
Return to the
comp.compilers page.
Search the
comp.compilers archives again.