RFR(M): 8201593: Print array length in ArrayIndexOutOfBoundsException.

[Lindenmaier, Goetz]

Hi,

yes, on ppc for example we pass it on the stack.
Before, it was passed in R0 which survives the call.
That worked, as it obviously worked so far on aarch 
for the register with the index.

Best regards,
  Goetz.

> -----Original Message-----
> From: aph at redhat.com [mailto:aph at redhat.com]
> Sent: Mittwoch, 25. April 2018 17:26
> To: Stuart Monteith <stuart.monteith at linaro.org>; Lindenmaier, Goetz
> <goetz.lindenmaier at sap.com>
> Cc: hotspot-compiler-dev at openjdk.java.net; aarch64-port-
> dev at openjdk.java.net; hotspot-runtime-dev at openjdk.java.net; aarch32-
> port-dev at openjdk.java.net
> Subject: Re: RFR(M): 8201593: Print array length in
> ArrayIndexOutOfBoundsException.
> 
> On 04/25/2018 04:00 PM, Stuart Monteith wrote:
> > I'm not quite sure to solve this yet - we'll need to use the stack in
> > some safe way.
> 
> It's not a great idea to pass arguments in rscratch1 or rscratch2.  These
> registers are for use in macros and should be treated as volatile.  Given
> that you're throwing an exception, registers will be clobbered anyway.
> 
> --
> Andrew Haley
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com>
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671