Displaying 4 results from an estimated 4 matches for "r327581".
2018 Jun 20
2
[RFC] Removing debug locations from ConstantSDNodes
...3
> incl do_something(%rip)
>
> Our users really wanted the line table entry for line 2 to include the constant materialization code for some VS debugger feature.
Got it. (For others following along, there's more discussion about this debugger feature in the commit description for r327581.)
> I think if you remove locations from ConstantSDNodes, you might want to add a late pass that propagates source locations backwards onto location-less instructions. This would also avoid some special cases when a basic block starts with an instruction that lacks location information. See Co...
2018 Jun 20
5
[RFC] Removing debug locations from ConstantSDNodes
..._something(%rip)
>
>
> Our users really wanted the line table entry for line 2 to include the constant materialization code for some VS debugger feature.
>
> Got it. (For others following along, there's more discussion about this debugger feature in the commit description for r327581.)
>
>
>
> I think if you remove locations from ConstantSDNodes, you might want to add a late pass that propagates source locations backwards onto location-less instructions. This would also avoid some special cases when a basic block starts with an instruction that lacks location inf...
2018 Mar 19
0
LLVM Weekly - #220, Mar 19th 2018
...performance improvements of up to ~30%.
[r327399](http://reviews.llvm.org/rL327399).
* `!dag` has been added to Tablegen, enabling programmatic construction of DAG
nodes. [r327492](http://reviews.llvm.org/rL327492).
* FastISel will now sink the materialisation of local values to their first
use. [r327581](http://reviews.llvm.org/rL327581).
* llvm-dsymutil has been renamed to dsymutil.
[r327790](http://reviews.llvm.org/rL327790).
## Clang commits
* The Clang C++ status page has been updated.
[r327769](http://reviews.llvm.org/rL327769).
* clang-tidy gained a Zircon module (Zircon forms the core...
2018 Jun 20
4
[RFC] Removing debug locations from ConstantSDNodes
Some time ago I saw a report of strange single-stepping behavior given Swift code that looks like this:
1| var input = [16, 14, 10, 9, 8, 7, 4, 3, 2, 1] //< Only number 1 is relevant.
2| print("start")
TL;DR: The debugger steps from line 2 -> 1 -> 2 in this code example. One clean way to fix this bug is to remove debug locations from ConstantSDNodes, and I'm asking if