Go to file
Andrew Burgess c2015ce4a4 gdb/testsuite: make test names unique in gdb.arch/*.exp
Make the test names unique in gdb.arch/*.exp by either modifying the
test names or using with_test_prefix.

I have also fixed a typo 'forth' -> 'fourth' throughout gdb.arch/*.

Finally, I replaced code like this:

  gdb_test "break [gdb_get_line_number "first breakpoint here"]" \
           "Breakpoint .* at .*${srcfile}.*" \
           "set first breakpoint in main"

With this:

  gdb_breakpoint [gdb_get_line_number "first breakpoint here"]

In those files that I was already modifying for the other reasons
given above.

gdb/testsuite/ChangeLog:

	* gdb.arch/amd64-byte.exp: Make test names unique, use
	gdb_breakpoint, and fix typo 'forth' -> 'fourth'.
	* gdb.arch/amd64-dword.exp: Likewise.
	* gdb.arch/amd64-pseudo.c: Fix typo 'forth' -> 'fourth'.
	* gdb.arch/amd64-stap-special-operands.exp: Make test names
	unique.
	* gdb.arch/amd64-tailcall-ret.exp: Likewise.
	* gdb.arch/amd64-word.exp: Make test names unique, use
	gdb_breakpoint, and fix typo 'forth' -> 'fourth'.
	* gdb.arch/i386-byte.exp: Make test names unique, use
	gdb_breakpoint.
	* gdb.arch/i386-word.exp: Likewise.
2020-08-27 16:32:40 +01:00
bfd Fix PR binutils/26356 on hppa*-*-hpux*. 2020-08-27 15:25:03 +00:00
binutils Fix PR binutils/26356 on hppa*-*-hpux*. 2020-08-27 15:25:03 +00:00
config Unify Solaris procfs and largefile handling 2020-07-30 15:41:50 +02:00
contrib
cpu bpf: add xBPF ISA 2020-08-26 15:39:00 +02:00
elfcpp
etc
gas PR26467 UBSAN: cgen.c:762 shift exponent 18446744073709551615 2020-08-27 21:56:33 +09:30
gdb gdb/testsuite: make test names unique in gdb.arch/*.exp 2020-08-27 16:32:40 +01:00
gdbserver gdb: allow specifying multiple filters when running selftests 2020-08-13 07:55:48 -04:00
gdbsupport gdb: allow specifying multiple filters when running selftests 2020-08-13 07:55:48 -04:00
gnulib Update gnulib to current trunk 2020-08-26 15:37:28 -07:00
gold PowerPC TPREL_HA/LO optimisation 2020-08-24 21:15:06 +09:30
gprof Unify Solaris procfs and largefile handling 2020-07-30 15:41:50 +02:00
include libctf, binutils, include, ld: gettextize and improve error handling 2020-08-27 13:15:43 +01:00
intl
ld Remove commit 9fb2400ce6 2020-08-27 13:52:45 +01:00
libctf libctf, binutils, include, ld: gettextize and improve error handling 2020-08-27 13:15:43 +01:00
libdecnumber Run autoreconf -vf throughout 2020-07-29 16:03:55 -04:00
libiberty
opcodes opcodes: Add missing entries to ebpf_isa_attr 2020-08-26 16:48:39 +02:00
readline
sim sim/bfin: include config/pkg.m4 in configure.ac 2020-08-21 11:55:08 -04:00
texinfo
zlib
.cvsignore
.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
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.