search for: reemphasize

...t-to-implement and maintain O(1), not O(N). I see no reason this would change in the future. • On whether the back-end need be involved. As I've already discussed WRT stack layout, the back-end must be involved because only it knows how stack frames and code are laid out. I'd like to reemphasize that back ends can and do introduce or delete both control flow and calls in the program--adding safe points which are not (as such) represented in LLVM IR. Thus, the front-end cannot know even the set of all safe points (much less their locations). From that, it follows that liveness and...

Gordon Henriksen wrote: > > The "runtime interface" is a historical artifact. LLVM does not impose > a runtime library on its users. I wouldn't have a problem deleting all > mention of it, since LLVM does not impose a contract on the runtime. > Excellent, I found it somewhat unhelpful! >> The semantics of llvm.gcroot are vague: >> "At