[jdk18] RFR: 8274323: compiler/codegen/aes/TestAESMain.java failed with "Error: invalid offset: -1434443640" after 8273297

[Smita Kamath]

On Thu, 16 Dec 2021 07:24:11 GMT, Vladimir Kozlov <kvn at openjdk.org> wrote:

>> The failure happens with XX:+DeoptimizeAlot option. I've set reexecute bit and reset the appropriate state for the interpreter to execute the code when deoptimization occurs.
>
> Unfortunately I hit assert during CTW testing on Windows-x64 when compiling `com.sun.crypto.provider.GaloisCounterMode::implGCMCrypt`.
> 
> 
> #  Internal Error (t:\workspace\open\src\hotspot\share\opto\graphKit.cpp:250), pid=41320, tid=43308
> #  assert(ex_map->jvms()->same_calls_as(_exceptions->jvms())) failed: all collected exceptions must come from the same place
> 
> Current CompileTask:
> C2:   7834 2950    b  4       com.sun.crypto.provider.GaloisCounterMode::implGCMCrypt (100 bytes)
> 
> Stack: [0x000000c86a600000,0x000000c86a700000]
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
> V  [jvm.dll+0xbb90d1]  os::platform_print_native_stack+0xf1  (os_windows_x86.cpp:235)
> V  [jvm.dll+0xdf904e]  VMError::report+0x101e  (vmError.cpp:828)
> V  [jvm.dll+0xdfaa4e]  VMError::report_and_die+0x7fe  (vmError.cpp:1656)
> V  [jvm.dll+0xdfb1d4]  VMError::report_and_die+0x64  (vmError.cpp:1437)
> V  [jvm.dll+0x536f47]  report_vm_error+0xb7  (debug.cpp:280)
> V  [jvm.dll+0x6da439]  GraphKit::add_exception_states_from+0x119  (graphKit.cpp:286)
> V  [jvm.dll+0x414375]  PredicatedIntrinsicGenerator::generate+0x7f5  (callGenerator.cpp:1358)
> V  [jvm.dll+0x5c3b62]  Parse::do_call+0x9c2  (doCall.cpp:651)
> V  [jvm.dll+0xbe3745]  Parse::do_one_bytecode+0x32b5  (parse2.cpp:2704)
> V  [jvm.dll+0xbd5ae7]  Parse::do_one_block+0x437  (parse1.cpp:1557)
> V  [jvm.dll+0xbd463c]  Parse::do_all_blocks+0x5cc  (parse1.cpp:710)
> V  [jvm.dll+0xbd0c3d]  Parse::Parse+0xc1d  (parse1.cpp:616)
> V  [jvm.dll+0x413a15]  ParseGenerator::generate+0xa5  (callGenerator.cpp:103)
> V  [jvm.dll+0x4eba90]  Compile::Compile+0x1110  (compile.cpp:714)
> 
> 
> The call stack has `PredicatedIntrinsicGenerator` so it seems related to changes.
> 
> I got replay file and will try to reproduce it tomorrow.

@vnkozlov Since, array allocation on heap is causing issues, would it be better if I update the code to have the temp array allocation on stack? The updated code will eliminate the need for re-execution.
I have the change ready and can push it if you think it is alright to do so. Please do let me know your thoughts. Thanks.

-------------

PR: https://git.openjdk.java.net/jdk18/pull/19