From: Godmar Back (gback@cs.utah.edu)
Date: Wed Feb 10 1999 - 01:12:25 EST
>
> As a side note, I've had some ideas on an incremental build system for
> Java (i.e., rebuilding a class whenever its source or any other
> dependency has changed), but I don't know when I'll have time to
> implement it :-(
Like I said, I'd prefer you do egcs. Build systems are fine and necessary,
but what really counts is what's being built.
>
> > For instance, one thing that Tim doesn't currently have the time to
> > do, but for which your skill set puts you in a formidable position
> > (I mean really), is to get the egcs front-end to run with Kaffe.
>
> I'm not sure I'm skilled enough to do that. I have never been able to
> learn enough about the internals of gcc :-(
My understanding is that you don't need to know a whole lot.
You just need to look at the assembly output gcj generates and how they
do exceptions.
>
> But I may find time to do it, it shouldn't be that hard. It would be
> still better to be able to use egcs' front-end and back-end as a
> just-in-time compiler. I already have some ideas on that, but I doubt
> I'll ever have enough time to evolve them into anything usable :-(
>
I'm not discarding the use of egcs front-end and back-end as a JIT.
However, this is not what is in reach. What it is reach is looking
at the egcs generated code, understand how they do metadata, trampolines,
synchronization and exceptions. All of which you understand. Then decide
whether to change Kaffe's metadata/trampolines/exceptions or whether to
change egcs. That's it. ;-)
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:58:04 EDT