| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Sort the remaining #include lines in include/... and lib/.... | Chandler Carruth | 2017-06-06 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | I did this a long time ago with a janky python script, but now clang-format has built-in support for this. I fed clang-format every line with a #include and let it re-sort things according to the precise LLVM rules for include ordering baked into clang-format these days. I've reverted a number of files where the results of sorting includes isn't healthy. Either places where we have legacy code relying on particular include ordering (where possible, I'll fix these separately) or where we have particular formatting around #include lines that I didn't want to disturb in this patch. This patch is *entirely* mechanical. If you get merge conflicts or anything, just ignore the changes in this patch and run clang-format over your #include lines in the files. Sorry for any noise here, but it is important to keep these things stable. I was seeing an increasing number of patches with irrelevant re-ordering of #include lines because clang-format was used. This patch at least isolates that churn, makes it easy to skip when resolving conflicts, and gets us to a clean baseline (again). llvm-svn: 304787 | ||||
| * | [Hexagon] Fix some Clang-tidy modernize and Include What You Use warnings; ↵ | Eugene Zelenko | 2016-12-13 | 1 | -21/+25 |
| | | | | | | | other minor fixes (NFC). llvm-svn: 289604 | ||||
| * | [Hexagon] Handle block live-ins with lane masks in HexagonBlockRanges | Krzysztof Parzyszek | 2016-10-18 | 1 | -1/+2 |
| | | | | | llvm-svn: 284522 | ||||
| * | [hexagon] Move BlockRanges and RDF stuff into the llvm namespace. | Benjamin Kramer | 2016-05-27 | 1 | -3/+2 |
| | | | | | | | No functional change intended. llvm-svn: 270980 | ||||
| * | [Hexagon] Optimize stack slot spills | Krzysztof Parzyszek | 2016-02-12 | 1 | -0/+240 |
| Replace spills to memory with spills to registers, if possible. This applies mostly to predicate registers (both scalar and vector), since they are very limited in number. A spill of a predicate register may happen even if there is a general-purpose register available. In cases like this the stack spill/reload may be eliminated completely. This optimization will consider all stack objects, regardless of where they came from and try to match the live range of the stack slot with a dead range of a register from an appropriate register class. llvm-svn: 260758 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|