mirror of
https://github.com/bminor/binutils-gdb.git
synced 2026-02-06 05:11:31 +00:00
c4b575f3b5
On s390 64-bit (s390x) compilers may save the SP, FP, and RA registers, which are of interest in SFrame, in other registers, such as floating- point registers, for instance when in a leaf function. SFrame does not explicitly track the SP. Instead SFrame relies on the architecture-specific CFA definition to recover the SP. The s390x ELF ABI [1] defines the CFA as SP at call site + 160, which results in the implicit SP recovery rule SP = CFA - 160. Assuming that CFI on s390 64-bit (s390x) adheres to the CFA definition, it is safe to ignore any CFI directives, that specify the SP register at entry to be saved either on the stack or in another register, as the SP can then always be recovered using the implicit SP recovery rule. [1]: s390x ELF ABI, https://github.com/IBM/s390x-abi/releases Committed-by: Indu Bhagat <indu.bhagat@oracle.com> gas/ * gen-sframe.c (sframe_xlate_do_register): Ignore .cfi_register SP on s390x. gas/testsuite/ * gas/cfi-sframe/cfi-sframe.exp (cfi-sframe-s390x-err-4): Rename test to cfi-sframe-s390x-sp-register. * gas/cfi-sframe/cfi-sframe-s390x-err-4.d: Rename to ... * gas/cfi-sframe/cfi-sframe-s390x-err-4.s: Likewise. * gas/cfi-sframe/cfi-sframe-s390x-sp-register.d: This. Test that .cfi_register SP is ignored. * gas/cfi-sframe/cfi-sframe-s390x-sp-register.s: Likewise. Add minimal assembler sample.
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.