Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2019-05-31T22:55:03+00:00 2019-05-31T22:55:03+00:00 Reid Kleckner rnk@google.com 2019-05-31T22:55:03+00:00 urn:sha1:eddd6c25b567bf2b75b38e9e09b80f69f87d7017 Testing with debuggers shows that our previous behavior was correct. The reason I thought MSVC did things differently is that MSVC prefers to use the 0xB combined code offset and code length update opcode when inline sites are discontiguous. Keep the test changes, and update the llvm-pdbutil inline line table dumper to account for this new interpretation of the opcodes. llvm-svn: 362277 2019-05-31T20:55:31+00:00 Reid Kleckner rnk@google.com 2019-05-31T20:55:31+00:00 urn:sha1:e98cf5fe47f2585363588d7cdd19c5bfe57f2c13 After improving the inline line table dumper in llvm-pdbutil and looking at MSVC's inline line tables, it is clear that setting the length of the inlined code region does not update the code offset. This means that the delta to the beginning of a new discontiguous inlined code region should be calculated relative to the last code offset, excluding the length. Implementing this is a one line fix for MC: simply don't update LastLabel. While I'm updating these test cases, switch them to use llvm-objdump -d and llvm-pdbutil. This allows us to show offsets of each instruction and correlate the line table offsets to the actual code. llvm-svn: 362264 2019-01-19T08:50:56+00:00 Chandler Carruth chandlerc@gmail.com 2019-01-19T08:50:56+00:00 urn:sha1:2946cd701067404b99c39fb29dc9c74bd7193eb3 to reflect the new license. We understand that people may be surprised that we're moving the header entirely to discuss the new license. We checked this carefully with the Foundation's lawyer and we believe this is the correct approach. Essentially, all code in the project is now made available by the LLVM project under our new license, so you will see that the license headers include that license only. Some of our contributors have contributed code under our old license, and accordingly, we have retained a copy of our old license notice in the top-level files in each project and repository. llvm-svn: 351636 2018-12-17T21:49:35+00:00 Reid Kleckner rnk@google.com 2018-12-17T21:49:35+00:00 urn:sha1:94ee0728e5e8665821ecfc20c2441e4bfc4e0bf2 This was a pre-existing bug that could be triggered with assembly like this: .p2align 2 .LtmpN: .cv_def_range "..." I noticed this when attempting to change clang to emit aligned symbol records. llvm-svn: 349403 2018-08-28T23:25:59+00:00 Reid Kleckner rnk@google.com 2018-08-28T23:25:59+00:00 urn:sha1:689f7733173c4a7757f10bc7442905c18274f288 Now that we create the label at the point of the directive, we don't need to set the "current CV location", and then later when we emit the next instruction, create a label for it and emit it. DWARF still defers the labels used in .debug_loc until the next instruction or value, for reasons unknown. llvm-svn: 340883 2018-05-18T19:46:24+00:00 Peter Collingbourne peter@pcc.me.uk 2018-05-18T19:46:24+00:00 urn:sha1:e3f652973e6e4fb7074b0bdc2291493e6cb8fae5 Provide some free functions to reduce verbosity of endian-writing a single value, and replace the endianness template parameter with a field. Part of PR37466. Differential Revision: https://reviews.llvm.org/D47032 llvm-svn: 332757 2018-04-25T23:34:15+00:00 Reid Kleckner rnk@google.com 2018-04-25T23:34:15+00:00 urn:sha1:2c6430fe3c2005a60680b72a52bfb4e81ca841ee If no data or instructions are emitted after a location directive, we should clear the cv_loc when we change sections, or it will be emitted at the beginning of the next section. This violates our invariant that all .cv_loc directives belong to the same section. Add clearer assertions for this. llvm-svn: 330884 2018-01-18T22:55:43+00:00 Reid Kleckner rnk@google.com 2018-01-18T22:55:43+00:00 urn:sha1:7897a789e7f138f928e3a9fecbb709ee043b44fe We did this for inline call site line tables, but we hadn't done it for regular function line tables yet. This patch copies that logic from encodeInlineLineTable. llvm-svn: 322905 2018-01-18T22:55:14+00:00 Reid Kleckner rnk@google.com 2018-01-18T22:55:14+00:00 urn:sha1:b5258722889112188d255140654163fdd4e1fbe7 I'm cleaning up this code before I attempt to fix a line table bug. llvm-svn: 322904 2018-01-12T18:05:40+00:00 Sam Clegg sbc@chromium.org 2018-01-12T18:05:40+00:00 urn:sha1:5e102eeee6ef0b6da3a4d683469e9954c000a09c We can probably take this a step further since the only user of the isUsed flag is AsmParser it should probably be doing this explicitly. For now this is a step in the right direction though. Differential Revision: https://reviews.llvm.org/D41971 llvm-svn: 322386