This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: assemble_external on .class files
- To: law@cygnus.com,Per Bothner <bothner@pacbell.net>
- Subject: Re: assemble_external on .class files
- From: Mark Klein <mklein@dis.com>
- Date: Tue, 25 May 1999 22:19:07 -0700
- Cc: egcs@egcs.cygnus.com,java-discuss@sourceware.cygnus.com
- References: <Your message of 25 May 1999 21:05:19 PDT. <m2n1yseark.fsf@magnus.cygnus.com>
At 10:44 PM 5/25/99 -0600, Jeffrey A Law wrote:
>Thanks. Hmmm, this makes me think that we're find with having them overloaded
>on the same bit. Mark, I think this is a red herring.
Could be, but then there's a problem with assemble_external vis the usage of
DECL_EXTERNAL for the vtable. Recall my earlier example, from
java::lang::Object:
Method name:"finalize" protected Signature: 4=()void
...
Method name:"hashCode" public native Signature: 11=()int
and the vtable:
__vt_10HelloWorld
.word _CL_10HelloWorld
.word 0
.word P%finalize__Q34java4lang6Object
.IMPORT hashCode__Q34java4lang6Object,CODE
.word P%hashCode__Q34java4lang6Object
.word P%equals__Q34java4lang6ObjectPQ34java4lang6Object
.word P%toString__Q34java4lang6Object
.IMPORT clone__Q34java4lang6Object,CODE
.word P%clone__Q34java4lang6Object
Note that in order to use the plabels, the symbols must first be imported on
PA-RISC. In this case, we have finalize, and it isn't native. However, in
order for assemble_external to emit the .IMPORT, DECL_EXTERNAL (among others)
must be true. But, hashCode is native and is imported, hence the .IMPORT.
Since this is in contradiction to usage in jc1 as explained by Per, I've
got a problem....
Jeff (or any other PA-RISC user) ... has anyone tried gcj/libjava on a HP9000?
Or is this a problem only on the HP3000?
G'night, y'all.
--
Mark Klein DIS International, Ltd.
http://www.dis.com 415-892-8400
PGP Public Key Available