Go to file
Bruno Larsen 07bb02de72 gdb/testsuite: Add a proc to test where compiler links the epilogue
Different compilers link the epilogue of functions to different lines.
As an example, gcc links it to the closing brace of the function,
whereas clang links it to the last statement of the function.  This
difference is important for the testsuite, since the where GDB will land
after a step can be wildly different.  Where possible, this dependency
should be side-stepped in the testsuite, but it isn't always possible,
so this commit adds a gdb_caching_proc that is able to detect where the
epilogue is linked, so tests can react accordingly.
2022-09-22 11:04:17 +02:00
bfd Automatic date update in version.in 2022-09-22 00:00:10 +00:00
binutils RISC-V: Implement Ztso extension 2022-09-21 11:43:35 +08:00
config
contrib
cpu
elfcpp
etc
gas RISC-V: Add macro-only operands to validate_riscv_insn 2022-09-22 06:28:19 +00:00
gdb gdb/testsuite: Add a proc to test where compiler links the epilogue 2022-09-22 11:04:17 +02:00
gdbserver gdbsupport: move include/gdb/fileio.h contents to fileio.h 2022-09-21 14:11:03 -04:00
gdbsupport gdbsupport: move fileio_errno_to_host to fileio.{h,cc} and rename 2022-09-21 14:11:03 -04:00
gnulib
gold New Serbian translations for various binutils sub-directories. 2022-09-20 11:33:16 +01:00
gprof bfd: Stop using -Wstack-usage=262144 when built with Clang 2022-09-14 05:42:17 +00:00
gprofng gprofng: fix -Wduplicated-cond warning 2022-09-21 19:00:00 -07:00
include gdbsupport: move include/gdb/fileio.h contents to fileio.h 2022-09-21 14:11:03 -04:00
intl
ld ld/testsuite: allow to force another directory for gcc linker 2022-09-22 09:23:18 +02:00
libbacktrace
libctf
libdecnumber
libiberty
opcodes RISC-V: Remove "b" operand type from disassembler 2022-09-22 06:28:19 +00:00
readline
sim sim/riscv: Complete tidying up with SBREAK 2022-09-05 09:42:06 +01:00
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
ar-lib
ChangeLog Maintainer mode: wrong gettext version? 2022-09-08 10:03:04 +01:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure configure: Pass CPPFLAGS_FOR_BUILD to subdirs 2022-09-21 06:14:16 +00:00
configure.ac configure: Pass CPPFLAGS_FOR_BUILD to subdirs 2022-09-21 06:14:16 +00:00
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 Maintainer mode: wrong gettext version? 2022-09-08 10:03:04 +01:00
setup.com
src-release.sh
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.