This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Don't generate NullPointerExceptions for arraylength and arrayload
- From: Ranjit Mathew <rmathew at gmail dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: GCJ Patches <java-patches at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 17 Mar 2005 13:08:03 +0530
- Subject: Re: Don't generate NullPointerExceptions for arraylength and arrayload
- References: <16952.32557.528504.580543@cuddles.cambridge.redhat.com>
Andrew Haley wrote:
> This removes the special case code that throws a NullPointerException
> bease on the type of an arrayref. This trick no longer works because
> in the bytecode front end we now use the same variable decl for every
> object. In ancy case, this optimization just provided a fast path to
> throw a NullPointerException.
>
> This is a regression from 3.x.
[...]
> - if (type == ptr_type_node)
> - return build3 (CALL_EXPR, int_type_node,
> - build_address_of (soft_nullpointer_node),
> - NULL_TREE, NULL_TREE);
> -
Doesn't doing this make "Array_3 -O3 bytecode -> native"
fail for you?
Thanks,
Ranjit.
--
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.hostingzero.com/