Displaying 2 results from an estimated 2 matches for "parceable".
2020 Sep 18
3
GC-parseable element atomic memcpy/memmove
...result in a
different lowering, which makes it possible to have a GC safepoint
during the copy operation.
There are three parts to the new lowering:
1) The calls with the new attribute will be wrapped into a statepoint
by RewriteStatepointsForGC (RS4GC). This way the stack at the calls
will be GC parceable.
2) Currently these intrinsics are lowered to GC leaf calls to the symbols
__llvm_{memcpy|memmove}_element_unordered_atomic_<element_size>.
The calls with the new attribute will be lowered to calls to different
symbols, let's say
__llvm_{memcpy|memmove}_element_unordered_atomic_safepoint...
2020 Sep 30
2
GC-parseable element atomic memcpy/memmove
...result in a
different lowering, which makes it possible to have a GC safepoint
during the copy operation.
There are three parts to the new lowering:
1) The calls with the new attribute will be wrapped into a statepoint
by RewriteStatepointsForGC (RS4GC). This way the stack at the calls
will be GC parceable.
2) Currently these intrinsics are lowered to GC leaf calls to the symbols
__llvm_{memcpy|memmove}_element_unordered_atomic_<element_size>.
The calls with the new attribute will be lowered to calls to different
symbols, let's say
__llvm_{memcpy|memmove}_element_unordered_atomic_safepoint...