Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | MachineOperand/MIParser: Do not print debug-use flag, infer it | Matthias Braun | 2018-10-30 | 1 | -1/+1 |
| | | | | | | | | | | | | | | The debug-use flag must be set exactly for uses on DBG_VALUEs. This is so obvious that it can be trivially inferred while parsing. This will reduce noise when printing while omitting an information that has little value to the user. The parser will keep recognizing the flag for compatibility with old `.mir` files. Differential Revision: https://reviews.llvm.org/D53903 llvm-svn: 345671 | ||||
* | [WebAssembly] Move/clone DBG_VALUE during WebAssemblyRegStackify pass | Yury Delendik | 2018-09-25 | 1 | -0/+82 |
Summary: The MoveForSingleUse or MoveAndTeeForMultiUse functions move wasm instructions, however DBG_VALUE stay unchanged -- moving or cloning these. Reviewers: dschuff Reviewed By: dschuff Subscribers: mattd, MatzeB, dschuff, sbc100, jgravelle-google, aheejin, sunfish, llvm-commits, aardappel Tags: #debug-info Differential Revision: https://reviews.llvm.org/D49034 llvm-svn: 343007 |