Go to file
Jan Beulich e2b983d47e x86-64: allow HLE store of accumulator to absolute 32-bit address
In commit 1212781b35 ("ix86: allow HLE store of accumulator to
absolute address") I was wrong to exclude 64-bit code. Dropping the
check also leads to better diagnostics in 64-bit code ("MOV", after
all, isn't invalid with "XRELEASE").

While there also limit the amount of further checks done: The operand
type checks that were there were effectively redundant with other ones
anyway, plus it's quite fine to also have "xrelease mov <disp>, %eax"
look for the next MOV template (in fact again also improving
diagnostics).
2022-12-12 13:52:47 +01:00
bfd PR29892, Field file_table of struct module is uninitialized 2022-12-12 19:25:19 +10:30
binutils PR29872, uninitialised value in display_debug_lines_decoded dwarf.c:5413 2022-12-12 19:25:19 +10:30
config
contrib
cpu
elfcpp
etc
gas x86-64: allow HLE store of accumulator to absolute 32-bit address 2022-12-12 13:52:47 +01:00
gdb [gdb/tdep] Fix larl handling in s390_displaced_step_fixup 2022-12-10 15:40:34 +01:00
gdbserver [aarch64] Add TPIDR2 register support for Linux 2022-12-09 13:41:15 +00:00
gdbsupport
gnulib
gold
gprof
gprofng gprofng: remove unused gprofng/src/DbeSession.cc.1 2022-11-28 20:52:10 -08:00
include libsframe: rename API sframe_fde_func_info to sframe_fde_create_func_info 2022-12-09 10:25:31 -08:00
intl
ld x86-64: Remove BND from 64-bit IBT PLT 2022-12-08 08:05:45 -08:00
libbacktrace testsuite: support mold linker 2022-12-05 15:52:51 +01:00
libctf libctf: avoid potential double free 2022-12-08 11:46:22 +10:30
libdecnumber
libiberty
libsframe libsframe: rename API sframe_fde_func_info to sframe_fde_create_func_info 2022-12-09 10:25:31 -08:00
opcodes x86: re-work insn/suffix recognition 2022-12-12 13:51:46 +01:00
readline
sim
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
ar-lib
ChangeLog
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
README
README-maintainer-mode
setup.com
src-release.sh src-release.sh: Fix gdb source tarball build failure due to libsframe 2022-11-30 07:32:58 +04:00
symlink-tree
test-driver
ylwrap

		   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.