|Just-In-Time C/C++ Compilation firstname.lastname@example.org (Charles A Erignac) (1999-06-12)|
|Re: Just-In-Time C/C++ Compilation Renaud.Marlet@irisa.fr (Renaud Marlet) (1999-06-14)|
|Re: Just-In-Time C/C++ Compilation email@example.com (Ben Hirsh) (1999-06-19)|
|From:||Charles A Erignac <firstname.lastname@example.org>|
|Date:||12 Jun 1999 21:30:52 -0400|
|Organization:||Center for Human Modeling and Simulation|
|Keywords:||C, question, comment|
I am currently working on a numerical simulation modeling
language. The domain of application (hydraulic system (dis)assembly)
precludes any kind of a priori compilation. The first version of the
simulator was an interpretor. I am thinking about just-in-time
compilation for the second version.
Here is my idea:
- The simulator runs as an interpretor but uses a C or C++ compiler
to convert its arithmetic operations (linear system solving, and
integration) and support logic into a dynamic library.
- The compilation is a background process.
- The simulator runs as an interpreter until the compilation is
completed. At that point, the dynamic library is loaded and replaces the
Did anyone try this method? Are there any papers treating this subject?
Are there better alternatives?
I thank you in adavnce for your answers.
[Seems like it'd be easy enough to run your local C compiler, created a
shared library, and then dlopen() it, although the overhead would be
pretty astonishing. -John]
Return to the
Search the comp.compilers archives again.