Mayank Agrawal f23292d8a7 Cygwin: gendef: fix AArch64 _sigfe_maybe control flow
_sigfe_maybe returned on both outcomes of the 'TLS initialized?' check,
so it never entered _sigfe and never called the wrapped function.

The wrapper enters it with 'br' after reserving 16 bytes and storing the
real function address at [sp], but AArch64 'ret' branches to x30 and
pops nothing, so the bypass path returned without calling the function
while leaking the wrapper slot.

Branch to a shared L_sigfe_entry label when TLS is valid, mirroring the
x86_64 path's "je 1f", and otherwise pop the wrapper slot and tail-call
the real function through it.

The CYGTLS_INITIALIZED comparison also built 0x173fc763 instead of
0xc763173f, as the movz/movk halves were swapped, so it could never
match.

Fixes: ae46abc226 ("Cygwin: gendef: add _sigfe_maybe for TLS initialization checks on AArch64")
Signed-off-by: Aswin Kalies <aswin.kalies@multicorewareinc.com>
2026-09-27 14:55:31 +01:00
2021-11-10 20:14:00 -05:00
2015-03-09 20:53:11 +01:00
2016-03-22 10:25:20 +01:00
2016-03-22 10:25:20 +01:00
2021-02-24 11:03:28 +01:00
…
…
2016-03-22 10:25:20 +01:00
2016-03-22 10:25:20 +01:00
2016-03-22 10:25:20 +01:00
2010-01-09 21:11:32 +00:00
2014-02-05 13:17:47 +00:00
2010-01-09 21:11:32 +00:00
2010-01-09 21:11:32 +00:00
2016-06-23 15:54:55 -04:00
2016-03-22 10:25:20 +01:00
2016-03-22 10:25:20 +01:00
…
2016-03-22 10:25:20 +01:00

		   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.
S
Description
No description provided
Readme GPL-2.0
144 MiB
0 Stars 1 Watchers 0 Forks
Languages
C 60.8%
Makefile 19.2%
C++ 10.3%
Assembly 5%
Linker Script 1.2%
Other 3.3%