[llvm-dev] RFC Storing BB order in llvm::Instruction for faster local dominance (original) (raw)
Sanjoy Das via llvm-dev llvm-dev at lists.llvm.org
Mon Oct 15 09:41:15 PDT 2018
- Previous message: [llvm-dev] RFC Storing BB order in llvm::Instruction for faster local dominance
- Next message: [llvm-dev] How to properly initialize a callgraph pointer?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Oct 15, 2018 at 8:00 AM Sanjoy Das <sanjoy at playingwithpointers.com> wrote:
Would it make sense to put a uint64 epoch number in a basic block which would be incremented every time there was a change? You could use that to more easily invalidate OBBs I think, and it may be useful in other situations too. We could perhaps generalize this and keep two epoch numbers, one for insertions and one for deletions, and only use the deletion epoch to invalidate OBBs (but then OBBs would have to have value handles).
Sorry I meant only use the insertion epoch to invalidate OBBs.
-- Sanjoy
- Previous message: [llvm-dev] RFC Storing BB order in llvm::Instruction for faster local dominance
- Next message: [llvm-dev] How to properly initialize a callgraph pointer?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]