mirror of
https://github.com/gcc-mirror/gcc.git
synced 2026-05-06 14:59:39 +02:00
ab240ab509
_ITM_beginTransaction is a 'returns_twice' function that saves x30 on the stack as part of gtm_jmpbuf (that is passed down to GTM_begin_transaction), but the saved x30 is also used for return. The return path should be protected so we don't leave an ldp x29, x30, [sp] ret gadget in the code, so x30 is signed on function entry. This exposes the signed address in the gtm_jmpbuf too. The jmpbuf does not need a signed address since GTM_longjmp uses ldp x29, x30, [x1] br x30 and with BTI there is a BTI j at the _ITM_beginTransaction call site where this jump returns. Using PAC does not hurt: the gtm_jmpbuf is internal to libitm and its layout is only used by sjlj.S so the signed address does not escape. Saving signed x30 into gtm_jmpbuf provides a bit of extra protection, but more importantly it allows adding the PAC-RET support without changing the existing code much. In theory bti and pac-ret protection can be added unconditionally since the instructions are in the nop space, in practice they can cause trouble if some tooling does not understand the gnu property note (e.g. old binutils) or some unwinder or debugger does not understand the new dwarf op code used for pac-ret (e.g old gdb). So the code is written to only support branch-protection according to the code generation options. libitm/ChangeLog: * config/aarch64/sjlj.S: Add conditional pac-ret protection.
This directory contains the GNU Compiler Collection (GCC). The GNU Compiler Collection is free software. See the files whose names start with COPYING for copying permission. The manuals, and some of the runtime libraries, are under different terms; see the individual source files for details. The directory INSTALL contains copies of the installation information as HTML and plain text. The source of this information is gcc/doc/install.texi. The installation information includes details of what is included in the GCC sources and what files GCC installs. See the file gcc/doc/gcc.texi (together with other files that it includes) for usage and porting information. An online readable version of the manual is in the files gcc/doc/gcc.info*. See http://gcc.gnu.org/bugs/ for how to report bugs usefully. Copyright years on GCC source files may be listed using range notation, e.g., 1987-2012, indicating that every year in the range, inclusive, is a copyrightable year that could otherwise be listed individually.