search for: d11933

Displaying 3 results from an estimated 3 matches for "d11933".

Did you mean: 511933
2015 Aug 12
3
[LLVMdev] Improving the quality of debug locations / DbgValueHistoryCalculator
Hi all, An early implementation of extending debug ranges and providing multiple location support is done here: http://reviews.llvm.org/D11933 Design document: https://docs.google.com/document/d/1noDVWTvTWBdYdweICPBwvwyt8QvX4KHl7j3XKNSg1nE/edit?usp=sharing On Jun 24, 2015, at 12:12 PM, Alexey Samsonov <vonosmas at gmail.com> wrote: Hi Adrian, You might want to take a look at abandoned http://reviews.llvm.org/D2658 <https://ur...
2015 Sep 21
3
Fwd: extending liveness of 'this' pointer via FAKE_USE opcode
Oops, forgot to reply-all (& adding a few other people to the 'to' line) ---------- Forwarded message ---------- From: David Blaikie <dblaikie at gmail.com> Date: Mon, Sep 21, 2015 at 11:22 AM Subject: Re: [llvm-dev] extending liveness of 'this' pointer via FAKE_USE opcode To: "Pieb, Wolfgang" <Wolfgang_Pieb at playstation.sony.com> On Mon, Sep 21,
2015 Dec 26
2
Proposal for multi location debug info support in LLVM IR
...work for describing the locations of source variables in the optimization pipeline to improve debug info quality. This proposal concerns the IR format for encoding this information. Separately, getting this info into DWARF will require additional work, some of which has already been done in D11933 and D11986. The backend work is outside the scope of this proposal. # Goals of this design I tried to come up with a scheme that is a minimal modification of the existing mechanism to ease upgrading for both frontends and optimizers, but still separates the three concerns I think are required for...