This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: generic type support
- From: Tom Tromey <tromey at redhat dot com>
- To: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- Cc: "Geert Bevin" <gbevin at uwyn dot com>, <java at gcc dot gnu dot org>
- Date: 19 Feb 2003 13:48:16 -0700
- Subject: Re: generic type support
- References: <41D1051F31A2674C99E41CA28EE734980A1F83@isp-ex2k.intellimade.net>
- Reply-to: tromey at redhat dot com
>>>>> "Øyvind" == Øyvind Harboe <oyvind dot harboe at zylin dot com> writes:
Øyvind> I was surprised to find that GCJ has a frontend at all.
Øyvind> Why?
Øyvind> It seems like this problem has been thoroughly put to bed by e.g.
Øyvind> Jikes, javac, etc.
It is a "natural" thing to do. And it is certainly convenient, though
perhaps the convenience could be addressed by teaching gcj how to
invoke a bytecode compiler. Maybe there are strange failure modes
involved in doing this.
Relying on javac was never an option (except at the very early days
when only the bytecode front end was working). javac isn't free
software.
Were there free compilers around when gcj was started? I don't
remember.
Anyway, more practically, the bytecode front end still generates worse
code. I think we know how to fix it, but nobody is working on it.
Teaching gcj to invisibly run jikes and then read the resulting
bytecode would be an interesting project.
Tom