[NativeAOT] Enable software writewatch and card bundles on Windows.

[VSadov]

Fixes: #75110

This is mostly adding support for writewatch and card bundles in the Windows GC barriers.

Also did some cleanups to

• make Unix and Windows write barriers in NativeAOT as similar as possible.
• change ARM64 barriers to a more compact pattern, as used in CoreClr barriers.
  (tailcall chain of Ref->Checked->Unchecked, not doing stlr when write is not to the heap, etc..)
• trash the same registers in ARM64 barriers as in CoreClr
  (RiuJIT allows some freedom in scratch register use, but it is better to be similar here)

[VSadov]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[teo-tsirpanis]

@VSadov to make GitHub close the issue you have to separate it with a space like Fixes #75110.

[VSadov]

@teo-tsirpanis Thanks! I was wondering why it works sometimes

[VSadov]

Lots of failures in Frozen dictionaries tests. Are they supposed to fail on NativeAOT? @stephentoub

[VSadov]

the failures are #78046

[jkotas]

CoreCLR versions of these write-barriers use pattern like this:

 test byte ptr [rcx + r10], al
je SetCardTableBit_ByRefWriteBarrier
REPRET
SetCardTableBit_ByRefWriteBarrier:

It makes the hot path of the write barrier fit into fewer cache lines and it makes the jump better statically predicted (forward conditional branches are predicted not taken by default).

[jkotas]

(It does not look easy to retrofit this pattern into the native AOT write barriers. You can ignore this feedback.)

[jkotas]

CoreCLR write barriers seem to be using more efficient pattern to access the statics on arm64. Do you happen to know how much does it save?

[VSadov]

Are you referring to the version that patches constants in the code?
I think accessing inline constants is a bit more compact, but on arm64 it is not as nice as on x64 as you can't just load an immediate value, and CPU is likely trained to recognize the indirect load pattern.
Otherwise, these are values that change extremely rarely, so they would be in every cache. In terms of cache misses it is similar cost, but skips an indirection.

We could implement the scheme with patching inline constants and it is likely to be an improvement, but likely too small to consider it an urgency.

[jkotas]

LGTM. Thank you!

[VSadov]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[VSadov]

The only NativeAOT failure is #76501 (which is known and fixed already)

[VSadov]

Thanks!!