This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Java: fix Array_3 byte compiler failures
- From: Per Bothner <per at bothner dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, java at gcc dot gnu dot org
- Date: Thu, 26 Sep 2002 10:36:09 -0700
- Subject: Re: Java: fix Array_3 byte compiler failures
- References: <15763.15643.641635.382646@cuddles.cambridge.redhat.com>
Andrew Haley wrote:
The test case Array_3.java (compilation from bytecode) has been
failing for a while. It turns out that we can't compile `aconst_null;
arraylength' because build_java_array_length_access() insists that its
arg is of type array, whereas null_pointer_node is of type (void *).
Why not just test for pointer_type_node? Or just null_pointer_node?
Actually, I think it would be cleaner to fix the tree representation.
The type of '(Object[]) null' should presumably be 'Object[]', not
'void*'. I.e. folding '(Object[]) null' to 'null' is I suspect wrong.
Are we stripping off a NOP_EXPR we shouldn't be?
--
--Per Bothner
per@bothner.com http://www.bothner.com/per/