craig vanderborgh <[EMAIL PROTECTED]> writes: > Hello, > > We are going to make a substantial attempt to get Derby running on GCJ. The > goal is not to run Derby on the GCJ "JVM", but instead to ahead-of-time > compile > all the Derby sources (to .o files using the gcj compiler) so that the results > are compact and fast enough to use on embedded systems.
As I said in my reply to Steve Stewart: A really cool idea! I would really like to compare the performance of a native Derby to one running inside a JVM. > > We plan on using GCJ 3.3.2, or perhaps 4.x. What are the primary porting > issues we're likely to encounter, and how do you think we ought to address > them > in a way that might eventually be of use to the Derby project? > > Please advise. Can't give much. But read Steve's post (if you haven't already done so), especially what he says about the FSF Classpath project. -- dt
