Displaying 4 results from an estimated 4 matches for "rewritestatepoints".
2016 Mar 03
2
Status of Garbage Collection with Statepoints in LLVM
...y replace gcroot. So we wanted to try out the statepoints
approach.
Though it turned out that:
* the pass for inserting statepoints is hard-coded to only work with
samples and CLR (see [placesafepoints])
* the pass for rewriting statepoints is hard-coded to only work with
samples and CLR (see [rewritestatepoints])
* the only backend supporting statepoints right now seems to be 64-bit
intel (see [backend-x64])
Since the ARM backend (and e.g. 32-bit intel) doesn't seem to have support
for lowering statepoints-using IR, we were rather disappointed.
We are now experimenting with keeping a shadow stack...
2016 Sep 30
2
Adding utility/debugging passes upstream
...wondering what’s the community guideline for adding new passes which are solely used for debugging/analysis purposes? Can this be in the upstream llvm, or such passes are more suitable in local downstream repository?
In our case, the ‘utility (ease-of-analysis)’ pass is for transformation done by RewriteStatepointsForGC (RS4GC). Note that right now, RS4GC is not enabled in the opt pipeline upstream, but the utility pass would be for downstream users who have RS4GC enabled in their opt pipeline.
I think you should start by describing exactly what the pass is doing and how it is useful for working with/on Rewr...
2016 Sep 30
2
Adding utility/debugging passes upstream
...wondering what’s the community guideline for adding new passes which are solely used for debugging/analysis purposes? Can this be in the upstream llvm, or such passes are more suitable in local downstream repository?
In our case, the ‘utility (ease-of-analysis)’ pass is for transformation done by RewriteStatepointsForGC (RS4GC). Note that right now, RS4GC is not enabled in the opt pipeline upstream, but the utility pass would be for downstream users who have RS4GC enabled in their opt pipeline.
Thanks,
Anna
2016 Mar 04
2
Status of Garbage Collection with Statepoints in LLVM
...les +
PlaceSafepoints should be enough for both deoptimization and precise
relocating GC.
If you don't need to *poll* for safepoints at all (perhaps the entire
VM is fully single threaded, so you safepoint only on allocation),
then PlaceSafepoints is not needed at all, and you can directly run
RewriteStatepointsForGC.
-- Sanjoy