Deduce the memory behavior, aka "read-none", "read-only", or
"write-only", for functions and arguments.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
- Build Status
Buildable 37939 Build 37938: arc lint + arc unit
Event Timeline
Comment Actions
Overall, I think the logic is sound.
llvm/lib/Transforms/IPO/Attributor.cpp | ||
---|---|---|
420 | It is based on the explicit rule that SubsumingPositionIterator must iterate the corresponding IRPosition first. I think you should mention this rule somewhere in SubsumingPositionIterator implementation or header. | |
3228–3230 | style: remove bracket | |
3306–3312 | Maybe it is necessary to look at other atomic memory instructions also. |
It is based on the explicit rule that SubsumingPositionIterator must iterate the corresponding IRPosition first. I think you should mention this rule somewhere in SubsumingPositionIterator implementation or header.