Go to file
Tom de Vries 0dbca2abb9 [gdb/testsuite] Remove KFAIL for PR ada/30908
PR ada/30908 turns out to be a duplicate of PR ada/12607, which was fixed by
commit d56fdf1b97 ("Refine Ada overload matching").

Remove the KFAILs for PR ada/30908.

Tested on x86_64-linux.

Approved-By: Tom Tromey <tom@tromey.com>

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30908
2024-02-27 16:21:56 +01:00
bfd s390: Add r_offset check to the weak undef change 2024-02-27 15:24:14 +01:00
binutils x86: also permit YMM/ZMM use in CFI directives 2024-02-23 11:59:09 +01:00
config
contrib
cpu
elfcpp x86-64: Add R_X86_64_CODE_6_GOTTPOFF 2024-02-08 03:45:43 -08:00
etc
gas aarch64: rename internals related to PAuth feature to use pauth in their naming for coherency 2024-02-27 12:46:15 +00:00
gdb [gdb/testsuite] Remove KFAIL for PR ada/30908 2024-02-27 16:21:56 +01:00
gdbserver gdb: Modify the output of "info breakpoints" and "delete breakpoints" 2024-02-26 19:19:58 +08:00
gdbsupport Fix throw_winerror_with_name build error on x86-64 Cygwin 2024-02-23 17:24:17 +00:00
gnulib
gold x86-64: Add R_X86_64_CODE_6_GOTTPOFF 2024-02-08 03:45:43 -08:00
gprof
gprofng gprofng: Add hardware counter profiling for the Ampere system 2024-02-25 17:30:35 -08:00
include aarch64: rename internals related to PAuth feature to use pauth in their naming for coherency 2024-02-27 12:46:15 +00:00
ld s390: Avoid reloc overflows on undefined weak symbols 2024-02-27 14:07:17 +01:00
libbacktrace
libctf
libdecnumber
libiberty
libsframe
opcodes aarch64: rename internals related to PAuth feature to use pauth in their naming for coherency 2024-02-27 12:46:15 +00:00
readline
sim sim: no rule to make sim/ppc/Makefile.in 2024-02-24 11:52:10 +10:30
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
ar-lib
ChangeLog
compile
config-ml.in
config.guess
config.rpath
config.sub
configure Fix disabling of year 2038 support on 32-bit hosts by default 2024-02-05 15:28:05 -03:00
configure.ac Fix disabling of year 2038 support on 32-bit hosts by default 2024-02-05 15:28:05 -03: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
SECURITY.txt
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.