search for: creategcmachinecodeanalysispass

..., which would insert user-defined code for safe points. Unfortunately, code inserted there would stick around in the IR after the machine code was emitted, and if the function were JITted again, we'd get duplicate safe points. Another way to do it might be to add a MachineFunction pass next to createGCMachineCodeAnalysisPass() (or instead of it), which could emit appropriate MachineInstructions to implement the safe point. This, of course, forces safe points to be written in MachineInstructions instead of IR instructions, which isn't ideal. Another way might be to run a pass over the IR inserting llvm.safepoint()...

...er the machine code was emitted, and if the function > were JITted again, we'd get duplicate safe points. Unfortunately, I don't believe this is workable. It would make this work much easier if it were. > Another way to do it might be to add a MachineFunction pass next to > createGCMachineCodeAnalysisPass() (or instead of it), which could > emit appropriate MachineInstructions to implement the safe point. > This, of course, forces safe points to be written in > MachineInstructions instead of IR instructions, which isn't ideal. I think this is the way to go, though it's also t...

...de was emitted, and if the function were JITted again, > we'd get duplicate safe points. > > > Unfortunately, I don't believe this is workable. It would make this work > much easier if it were. > > Another way to do it might be to add a MachineFunction pass next > to createGCMachineCodeAnalysisPass() (or instead of it), which could > emit appropriate MachineInstructions to implement the safe point. This, > of course, forces safe points to be written in MachineInstructions instead > of IR instructions, which isn't ideal. > > > I think this is the way to go, though it'...