RFR: 8329331: Intrinsify Unsafe::setMemory [v12]

[Scott Gibbons]

On Fri, 12 Apr 2024 00:23:33 GMT, Sandhya Viswanathan <sviswanathan at openjdk.org> wrote:

>> It would not be appropriate to add set memory marks to the existing _jbyte_fill as it is being used by other routines, and the effect of the mark will be very hard to track down (if any).
>> 
>> Are you *sure* we want to do that?
>
> Yes we want to do that. It is all guarded by thread->doing_unsafe_access() which is only true when we are getting to this code from unsafe. Similar technique is used in copyMemory as well.

Done.

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

PR Review Comment: https://git.openjdk.org/jdk/pull/18555#discussion_r1562573673