Thank you for telling us more about shuJIT. It's wonderful to have
several options for JITs for Java/Linux!
>If we pursuit real good performance, I think that we should deploy
>the intermediate representation such as GCC's RTL and perform more
>optimizations like C compiler and register allocation rather than
>direct translation like TYA and shuJIT.
I think you are right. Is anyone on the mailing list knowledgable
about what Cygnus is doing with gcc and Java? They have Java front end
and back ends for gcc now, but I believe they are targeting one-time
compilation rather than JIT. I sure wouldn't want the whole gcc image
in core for all my Java programs :-)
>Primary purpose of my development of JIT is having our thread
>migration system worked with JIT. Thread migration requires being
>able to take execution context out in machine independent form.
>Common JIT's don't allow us that.
Ah, I understand. Thread migration is an interesting topic - I'd love
to have it for my own research in mobile agents. Is there any
information online about your thread migration work?
>> The author is in a research group working on "OpenJIT",
>Sorry for misleading my writings, I'm not a member of
>OpenJIT project. I respect the leader of the project,
>Prof. Matsuoka and I'm very interesting in the project.
My apologies! I was looking at your web page and guessed you were
working with Prof. Matsuoka. I am very sorry for misstating your
affiliation.
