Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-java
Navigation:
Lists: gentoo-java: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: Hanno Meyer-Thurow <h.mth@...>
From: Karl Trygve Kalleberg <karltk@g.o>
Subject: Re: work on gcj for gentoo
Date: Tue, 21 Feb 2006 16:42:51 +0100
Hanno Meyer-Thurow wrote:
> Hi list!
> I would like to work on gcj for Gentoo.

Excellent! We need all the help we can get.

> I thought in a gcj-4.1 / ecj combination. Use ecj to bytecompile Java
> source to jar with gcj as backend. Then use gcj to create native
> executables or libraries out of that jar files. Creating a database
> via gcj-dbtool for jar / native code resolution. If possible Java to
> native.

The problem with this approach is your resulting programs will be
potentially rather slow.

While gcj can indeed compile .class files (inside .jars) to binary, I've
been told it can produce the most efficient of results. The source code
is much richer in structure than the bytecode, and opens up for many
effective optimizations which could only be reached through
"idiom-recognition" (which doesn't exist for gcj yet, afaik) of the
.class files.

I suspect that you shouldn't give up on using gcj as a source compiler
quite yet. This story may evolve with the whole ecj/gcjx/GPLv3 debate.

Just my 0.02CAD,

-- Karl T
-- 
gentoo-java@g.o mailing list


Replies:
Re: work on gcj for gentoo
-- Hanno Meyer-Thurow
References:
work on gcj for gentoo
-- Hanno Meyer-Thurow
Navigation:
Lists: gentoo-java: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
work on gcj for gentoo
Next by thread:
Re: work on gcj for gentoo
Previous by date:
work on gcj for gentoo
Next by date:
Re: work on gcj for gentoo


Updated Jun 17, 2009

Summary: Archive of the gentoo-java mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.