RFR: 8331033: EA fails with "EA unexpected CallLeaf unsafe_setmemory" after JDK-8329331

Scott Gibbons sgibbons at openjdk.org
Wed May 1 14:05:59 UTC 2024


Added a strcmp for unsafe_setmemory in process_call_arguments() so the assert would not trigger.

I believe this is the correct fix as I do not think the arguments for setMemory need special handling like arraycopy.

I would like suggestions on how to generate a testcase to catch this type of error in mainline.

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

Commit messages:
 - Add unsafe_setmemory comparison for process_call_arguments()

Changes: https://git.openjdk.org/jdk/pull/19032/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=19032&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8331033
  Stats: 2 lines in 1 file changed: 1 ins; 0 del; 1 mod
  Patch: https://git.openjdk.org/jdk/pull/19032.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/19032/head:pull/19032

PR: https://git.openjdk.org/jdk/pull/19032


More information about the hotspot-compiler-dev mailing list