search for: llvm_explicit_valu

Displaying 5 results from an estimated 5 matches for "llvm_explicit_valu".

Did you mean: llvm_explicit_value
2020 Jan 10
2
DW_OP_implicit_pointer design/implementation in general
...quot;. What changes do you have in mind there? Are you referring to the possibility of implicit values to refer to other variables? I'm sort of interested in maybe not doing that - and only implementing a more general form (what's been talked about with the LLVM_implicit_value (or was it LLVM_explicit_value? I forget)) - and synthesizing artificial variables in the backend rather than trying to track which variable a pointer points to. I think this would keep the impact on optimizations smaller & would be more general. My wager/belief/instinct is that most cases won't be pointing to a named v...
2020 Jan 13
2
DW_OP_implicit_pointer design/implementation in general
...in mind there? Are you referring to the > possibility of implicit values to refer to other variables? > > > > I'm sort of interested in maybe not doing that - and only implementing a > more general form (what's been talked about with the LLVM_implicit_value > (or was it LLVM_explicit_value? I forget)) - and synthesizing artificial > variables in the backend rather than trying to track which variable a > pointer points to. I think this would keep the impact on optimizations > smaller & would be more general. My wager/belief/instinct is that most > cases won't be p...
2020 Jan 14
2
DW_OP_implicit_pointer design/implementation in general
..., > > David wrote: > > Are you referring to the possibility of implicit values to refer to > other variables? I'm sort of interested in maybe not doing that - and only > implementing a more general form (what's been talked about with the > LLVM_implicit_value (or was it LLVM_explicit_value? I forget)) - and > synthesizing artificial variables in the backend rather than trying to > track which variable a pointer points to. I think this would keep the > impact on optimizations smaller & would be more general. > > Adrian wrote: > > If it were possible to synthe...
2020 Jan 08
2
DW_OP_implicit_pointer design/implementation in general
> On Jan 2, 2020, at 6:37 AM, Jeremy Morse <jeremy.morse.llvm at gmail.com> wrote: > > Hi all, > > On the topic of intrinsics, right now we have two (dbg.value / > dbg.addr) that respectively describe: > * The "direct value" (quoting langref) of a variable, and > * The address of where the current variable value is stored. > Both of which map onto dwarf
2020 Jul 21
2
DW_OP_implicit_pointer design/implementation in general
...;> >>> David wrote: >>> > Are you referring to the possibility of implicit values to refer to other variables? I'm sort of interested in maybe not doing that - and only implementing a more general form (what's been talked about with the LLVM_implicit_value (or was it LLVM_explicit_value? I forget)) - and synthesizing artificial variables in the backend rather than trying to track which variable a pointer points to. I think this would keep the impact on optimizations smaller & would be more general. >>> >>> Adrian wrote: >>> > If it were possible...