From 01eaae6dd12862cda6b42d565a215b07a178aba6 Mon Sep 17 00:00:00 2001 From: Djordje Todorovic Date: Tue, 9 Jul 2019 11:33:56 +0000 Subject: [DwarfDebug] Dump call site debug info Dump the DWARF information about call sites and call site parameters into debug info sections. The patch also provides an interface for the interpretation of instructions that could load values of a call site parameters in order to generate DWARF about the call site parameters. ([13/13] Introduce the debug entry values.) Co-authored-by: Ananth Sowda Co-authored-by: Nikola Prica Co-authored-by: Ivan Baev Differential Revision: https://reviews.llvm.org/D60716 llvm-svn: 365467 --- llvm/docs/LangRef.rst | 3 +++ 1 file changed, 3 insertions(+) (limited to 'llvm/docs/LangRef.rst') diff --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst index e15c0a3acb0..f98aa6270bb 100644 --- a/llvm/docs/LangRef.rst +++ b/llvm/docs/LangRef.rst @@ -4755,6 +4755,9 @@ The current supported opcode vocabulary is limited: ``DW_OP_entry_value`` may also appear after the ``AsmPrinter`` pass when a call site parameter value (``DW_AT_call_site_parameter_value``) is represented as entry value of the parameter. +- ``DW_OP_reg`` (or ``DW_OP_regx``) represents a physical register location. + The opcode is only generated by the ``AsmPrinter`` pass to describe + call site parameter value which requires an expression over two registers. DWARF specifies three kinds of simple location descriptions: Register, memory, and implicit location descriptions. Note that a location description is -- cgit v1.2.3