forked from Imagelibrary/binutils-gdb
dab5aee6dc
For the DW_OP_piece and DW_OP_bit_piece operations, in the DWARF 5 standard, it is stated that if the location description (of that piece) is empty, then the piece is describing an undefined location description. The act of allowing any location description to be placed on a DWARF stack means that now a new operations can be defined which could pop more then one location description from a DWARF stack. This means that the old rule is not really applicable any more and a new operation that explicitly pushes an undefined location description on the DWARF stack is needed. This new rule however is fully backward compatibility as described in the document found on: https://llvm.org/docs/AMDGPUDwarfExtensionsForHeterogeneousDebugging.html Under the new definitions for the DW_OP_piece and DW_OP_bit_piece operations. gdb/ChangeLog: * compile/compile-loc2c.c (compute_stack_depth_worker): Add support for new DW_OP_LLVM_undefined operations. * dwarf2/expr.c (dwarf_expr_context::execute_stack_op): Add support for new DW_OP_LLVM_undefined operations. * dwarf2/loc.c (dwarf2_get_symbol_read_needs): Add support for new DW_OP_LLVM_undefined operations. include/ChangeLog: * dwarf2.def (DW_OP): New DW_OP_LLVM_undefined operations enumeration. gdb/testsuite/ChangeLog: * gdb.dwarf2/dw2-llvm-undefined.exp: New test. Change-Id: I2064c8fa3c7bc6488a226082b807e802d6d943ab
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README; if with a libg++ release, see libg++/README, etc. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.