Please remove:
[non-normative] It may be used to determine the value of arguments
on entry to the current call frame provided they are not clobbered.
In this context.
It is not uncontroversial and conflicts with the existing text:
Or, when evaluating
DW_OP_entry_value, the consumer could virtually unwind using the Call Frame
Information (see Section 6.4 on page 171) to recover register values that might have
been clobbered since the subprogram entry point.
I think when Tony wrote that he had a slightly different notion of clobbered.
https://github.com/ccoutant/dwarf-locations/blob/2e9102f1248c3247be5611725216ddc90f0d8c32/002-clarifications-eval.txt#L654
Please remove: [non-normative] It may be used to determine the value of arguments on entry to the current call frame provided they are not clobbered. In this context. It is not uncontroversial and conflicts with the existing text: Or, when evaluating DW_OP_entry_value, the consumer could virtually unwind using the Call Frame Information (see Section 6.4 on page 171) to recover register values that might have been clobbered since the subprogram entry point. I think when Tony wrote that he had a slightly different notion of clobbered.