Go to file
Tom Tromey ea54f7806b Put "source" into DAP scope
I noticed a FIXME comment in the DAP code about adding a "source"
field to a scope.  This is easy to implement; I don't know why I
didn't do this originally.
2024-06-04 10:36:34 -06:00
bfd LoongArch: Make align symbol be in same section with alignment directive 2024-06-04 19:47:20 +08:00
binutils Update binutils release documentation to include using the -z option when invoking src-release.sh 2024-05-30 12:52:37 +01:00
config
contrib
cpu
elfcpp
etc
gas LoongArch: Make align symbol be in same section with alignment directive 2024-06-04 19:47:20 +08:00
gdb Put "source" into DAP scope 2024-06-04 10:36:34 -06:00
gdbserver
gdbsupport
gnulib
gold
gprof
gprofng gprofng: add hardware counters for AMD Zen4 2024-06-03 11:38:58 -07:00
include gas, aarch64: Add SVE2 lut extension 2024-05-28 17:28:29 +01:00
ld LoongArch: Disable linker relaxation if set the address of section or segment 2024-06-04 19:47:27 +08:00
libbacktrace
libctf libctf testsuite compilation failure 2024-05-23 08:11:12 +09:30
libdecnumber
libiberty
libsframe
opcodes x86/Intel: warn about undue mnemonic suffixes 2024-05-29 10:03:00 +02:00
readline
sim
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore .gitignore: ignore .vscode 2024-05-30 12:09:35 +01:00
.pre-commit-config.yaml gdb: bump black version to 24.4.2 2024-05-16 11:34:40 -04:00
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
SECURITY.txt
setup.com
src-release.sh src-release.sh: fix adjusting files permissions and cleaning 2024-06-04 14:59:08 +01: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.