mirror of
https://github.com/bminor/binutils-gdb.git
synced 2026-02-05 04:11:31 +00:00
a50279706b
For FDE type SFRAME_FDE_TYPE_FLEX, the offsets are not only laid out differently, they also have different encoding: - first data item is of unsigned type, it indicates the "Control Word" - second data item is of signed type, it indicates the "Offset Word" (The usage of "Word" above is colloquial, does not indicate a machine word of a specific size.) Adjust the APIs in libsframe to get stack frame offsets by adding a new argument type. Also add a new API to read the data items as unsigned types of the specified size: sframe_get_fre_udata. At the moment, like the generation routines in GAS, the textual dump routines in sframe-dump.c are also unaware of the FDE type SFRAME_FDE_TYPE_FLEX. In the next commits, these capabilities will be added. include/ * sframe-api.h (MAX_NUM_STACK_OFFSETS): Increase the number of stack offsets to 6 to accommodate the FDE type SFRAME_FDE_TYPE_FLEX. (sframe_get_fre_udata): New declaration. (sframe_fre_get_cfa_offset): Add new arg. (sframe_fre_get_fp_offset): Likewise. (sframe_fre_get_ra_offset): Likewise. libsframe/ * libsframe/sframe-dump.c (dump_sframe_func_with_fres): Pass SFRAME_FDE_TYPE_DEFAULT for FDE type. * sframe.c (sframe_fre_get_cfa_offset): Handle FDE type. (sframe_fre_get_fp_offset): Likewise. (sframe_fre_get_ra_offset): Likewise. * libsframe/libsframe.ver: Add new API sframe_get_fre_udata. libsframe/testsuite/ * libsframe.find/findfre-1.c: Pass SFRAME_FDE_TYPE_DEFAULT for FDE type. * libsframe.find/findfunc-1.c: Likewise. * libsframe.find/plt-findfre-1.c: Likewise. * libsframe.find/plt-findfre-2.c: Likewise.
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, and so on. 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.