Displaying 3 results from an estimated 3 matches for "entry_valu".
Did you mean:
entry_value
2020 Sep 01
4
[RFC] [DebugInfo] Using DW_OP_entry_value within LLVM IR
...The most interesting DWARF attribute for us (here) is DW_AT_call_value which contains a DWARF expression which represents a value of the parameter at the time of the call. For the context of this RFC, more relevant part of the feature is the callee side, and it refers to new DWARF operation - DW_OP_entry_value, used to indicate that in some situations we can use parameter’s entry value as a real value in the current frame. It relies on the call-site info provided, and the more DW_AT_call_value generated, the more debug location inputs using DW_OP_entry_value will be turned into real values.
Current imp...
2019 Feb 08
3
RFC: [DebugInfo] Improving Debug Information in LLVM to Recover Optimized-out Function Parameters
...fully implemented in internal Clang/LLVM 4.0 version.
> We presented a talk on our work at FOSDEM 2019[4].
>
Thank you for posting this. This looks very interesting! Since your proposal has a lot of different components, Sema support, DW_AT_call_site_parameter support, DW_OP_entry_value support, it will probably be best to split them out into separate reviews, but it's also good to discuss the proposal in its entirety first. I have a bunch of questions to make sure I fully understand what you are doing.
Sure, we will post several patches, each as a logical unit.
>...
2019 Feb 08
2
RFC: [DebugInfo] Improving Debug Information in LLVM to Recover Optimized-out Function Parameters
...ion.
> > We presented a talk on our work at FOSDEM 2019[4].
> >
>
> Thank you for posting this. This looks very interesting! Since your
> proposal has a lot of different components, Sema support,
> DW_AT_call_site_parameter support, DW_OP_entry_value support, it will
> probably be best to split them out into separate reviews, but it's also
> good to discuss the proposal in its entirety first. I have a bunch of
> questions to make sure I fully understand what you are doing.
>
> Sure, we will post several...