RFR(M): 8201593: Print array length in ArrayIndexOutOfBoundsException.
stuart.monteith at linaro.org
Wed Apr 25 15:49:10 UTC 2018
Indeed - and that is what I am seeing. Usually no parameters are being
called with this pattern, or rscratch1, with the temporary variable
being changed to use rscratch2 in such circumstances.
I'll try c_rarg1 and c_rarg2 - they should pass straight through,if I
interpret the code correcting.
On 25 April 2018 at 16:26, Andrew Haley <aph at redhat.com> wrote:
> 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
More information about the hotspot-runtime-dev