mirror of
https://github.com/bminor/binutils-gdb.git
synced 2026-02-05 21:31:38 +00:00
77a0bf4928
With the introduction of flex FDE type, handling .cfi_offset for
RA needs adjustment.
On architectures like x86_64, the return address (RA) is typically saved
at a fixed offset from the CFA. Previous versions of the SFrame format
assumed this fixed offset was invariant for the entire function on such
architectures. Consequently, GAS would warn and suppress SFrame
generation if it encountered a .cfi_offset directive for the RA
register that deviated from this fixed default.
SFrame V3 introduces "Flex FDEs" which allows tracking the RA location
explicitly even on architectures where it is usually fixed.
This patch updates sframe_xlate_do_offset () to leverage Flex FDEs. When
processing a .cfi_offset for the RA register:
- The check for non-representable RA offsets is relaxed. If the ABI
supports Flex FDEs (SFrame V3), GAS proceeds instead of issuing a
warning.
- For ABIs without explicit RA tracking (like AMD64), if the RA
offset differs from the default fixed offset, the FDE is marked as a
Flex FDE, and the new stack location is recorded.
- Logic is added to detect when the RA is restored to its standard
fixed offset. In this case, the tracking state is reset (ra_loc set
to SFRAME_FRE_ELEM_LOC_NONE), deferring to the ABI's default fixed RA
offset behavior.
gas/
* gen-sframe.c (sframe_xlate_do_offset): Support .cfi_offset for RA
by switching to Flex FDEs when necessary.
gas/testsuite/
* gas/cfi-sframe/cfi-sframe-x86_64-6.d: New test.
* gas/cfi-sframe/cfi-sframe-x86_64-6.s: New test to check
transition of location of REG_RA from register to CFA-8 (default
location on AMD64). Flex FDE in effect.
* gas/cfi-sframe/cfi-sframe.exp: Add new test.
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.