Indu Bhagat 6ea6536f01 gas: x86: ginsn: adapt the APX insn handling
A review comment on the SCFI V4 series was to bail out on APX
instructions differently:

Currently, GAS bails out at the mere sight of an APX instruction when
--scfi=experimental is in effect; this is implemented in form of an
early exit from x86_ginsn_new ().  It is preferable to not have to
handle APX instructions explicitly like that with an early exit,
but rather to use the existing infrastructure in the x86_ginsn_new ()
function to bail out only if the APX insn affects SCFI correctness.

FIXME -
1. There remains an outstanding issue with adcx etc ops
2. Add tests once above is fixed

gas/
	* config/tc-i386.c (ginsn_opsize_prefix_p): Rename and adjust to
	be ginsn_implicitstackop_opsize16_p instead.
	(x86_ginsn_enter): Use the new function.
	(x86_ginsn_leave): Likewise.
	(x86_ginsn_new): Likewise.  Also remove the stub for early exit
	for APX instructions.

gas/testsuite/
        * gas/scfi/x86_64/scfi-unsupported-insn-1.l:
2024-03-28 16:55:50 -07:00
2024-03-28 00:00:57 +00:00
2024-02-29 21:07:04 +10:30
2024-03-11 22:42:56 -04:00
2024-02-08 03:45:43 -08:00
2023-08-12 10:27:57 +09:30
2024-03-28 11:50:27 +01:00
2023-08-12 10:27:57 +09:30
2023-11-15 12:53:04 +00: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.
Description
Unofficial mirror of sourceware binutils-gdb repository. Updated daily.
Readme 897 MiB
Languages
C 50.6%
Makefile 22.6%
Assembly 13.2%
C++ 5.9%
Roff 1.5%
Other 5.6%