| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | [Analysis] Make LocationSize pretty-printing more descriptive | George Burgess IV | 2018-10-10 | 1 | -168/+168 |
| | | | | | | | | | | | | | | This is the third patch in a series intended to make https://reviews.llvm.org/D44748 more easily reviewable. Please see that patch for more context. The second being r344013. The intent is to make the output of printing a LocationSize more precise. The main motivation for this is that we plan to add a bit to distinguish whether a given LocationSize is an upper-bound or is precise; making that information available in pretty-printing is nice. llvm-svn: 344108 | ||||
| * | [AliasSetTracker] Do not treat experimental_guard intrinsic as memory ↵ | Max Kazantsev | 2018-08-15 | 1 | -48/+48 |
| | | | | | | | | | | | | | | | | | writing instruction The `experimental_guard` intrinsic has memory write semantics to model the thread-exiting logic, but does not do any actual writes to memory. Currently, `AliasSetTracker` treats it as a normal memory write. As result, a loop-invariant load cannot be hoisted out of loop because the guard may possibly alias with it. This patch makes `AliasSetTracker` so that it doesn't treat guards as memory writes. Differential Revision: https://reviews.llvm.org/D50497 Reviewed By: reames llvm-svn: 339753 | ||||
| * | [NFC] Add comprehensive test of AliasSetTracker with guards | Max Kazantsev | 2018-08-14 | 1 | -0/+1550 |
| llvm-svn: 339643 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|