This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Don't generate NullPointerExceptions for arraylength and arrayload

From: Tom Tromey <tromey at redhat dot com>
To: Andrew Haley <aph at redhat dot com>
Cc: Ranjit Mathew <rmathew at gmail dot com>, GCJ Patches <java-patches at gcc dot gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: 23 Mar 2005 15:50:13 -0700
Subject: Re: Don't generate NullPointerExceptions for arraylength and arrayload
References: <16952.32557.528504.580543@cuddles.cambridge.redhat.com><423933DB.8050104@gmail.com><16953.23491.946677.198244@cuddles.cambridge.redhat.com><39399b9d05031722596fb226ea@mail.gmail.com><16954.43604.687449.387392@cuddles.cambridge.redhat.com>
Reply-to: tromey at redhat dot com

>>>>> "Andrew" == Andrew Haley <aph@redhat.com> writes:

Andrew> In general, an aggressively optimising compiler is allowed to remove
Andrew> such loads, but the JLS doesn't permit it.

If we're going to leave this as-is, we should file a PR for it.  I
doubt real code ever runs into this case.  At the same time, it is
definitely a compliance bug.  I don't want us to be lax about
compliance, even though it is inconvenient at times.

Tom

References:
- Don't generate NullPointerExceptions for arraylength and arrayload
  - From: Andrew Haley
- Re: Don't generate NullPointerExceptions for arraylength and arrayload
  - From: Ranjit Mathew
- Re: Don't generate NullPointerExceptions for arraylength and arrayload
  - From: Andrew Haley
- Re: Don't generate NullPointerExceptions for arraylength and arrayload
  - From: Ranjit Mathew
- Re: Don't generate NullPointerExceptions for arraylength and arrayload
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]