Displaying 2 results from an estimated 2 matches for "d87954".
2020 Sep 18
3
GC-parseable element atomic memcpy/memmove
...st idea. This will not work if we want to do the same for non-atomic
intrinsics.
- Teach GC infrastructure to record base pointers for all derived
pointer arguments. This looks like an overkill for single use case.
Here is the proposed implementation in a single patch:
https://reviews.llvm.org/D87954
If there are no objections I will split it into individual reviews and
add langref changes.
Thoughts?
Artur
[1] An alternative approach would be to make the frontend generate a
chunked copy loop with a safepoint inside. The downsides are:
- It's harder for the optimizer to see that this loop...
2020 Sep 30
2
GC-parseable element atomic memcpy/memmove
...st idea. This will not work if we want to do the same for non-atomic
intrinsics.
- Teach GC infrastructure to record base pointers for all derived
pointer arguments. This looks like an overkill for single use case.
Here is the proposed implementation in a single patch:
https://reviews.llvm.org/D87954
If there are no objections I will split it into individual reviews and
add langref changes.
Thoughts?
Artur
[1] An alternative approach would be to make the frontend generate a
chunked copy loop with a safepoint inside. The downsides are:
- It's harder for the optimizer to see that this loop...