Go to file
Tom Tromey 6c412691f9 Avoid using DW_* macros in dwarf2/attribute.c
There's no need to use the DW_* accessor macros in dwarf2/attribute.c,
and this is a necessary step toward our goal of removing them
entirely.

gdb/ChangeLog
2020-09-29  Tom Tromey  <tom@tromey.com>

	* dwarf2/attribute.c (attribute::address): Don't use DW_UNSND or
	DW_ADDR.
	(attribute::string): Don't use DW_STRING.
	(attribute::get_ref_die_offset): Don't use DW_UNSND.
	(attribute::constant_value): Don't use DW_UNSND or DW_SND.
2020-09-29 20:29:06 -06:00
bfd Automatic date update in version.in 2020-09-30 00:00:06 +00:00
binutils binutils: dwarf.c handle DWARF5 DW_LLE_start_end and DW_LLE_start_length. 2020-09-29 14:08:51 +02:00
config sync libiberty from gcc 2020-09-08 20:12:57 +09:30
contrib Import mklog.py from gcc repo 2020-09-25 10:24:44 -04:00
cpu bpf: xBPF SDIV, SMOD instructions 2020-09-18 10:04:23 -07:00
elfcpp Re: Sync libiberty and include with GCC for get_DW_UT_name 2020-09-25 11:55:00 +09:30
etc
gas Add a note about recent changes to the AArch64 assembler: TRBE, ETE and ETMv4 system registers and Cortex-X1 enablement. 2020-09-29 16:43:57 +01:00
gdb Avoid using DW_* macros in dwarf2/attribute.c 2020-09-29 20:29:06 -06:00
gdbserver Handle 64bit breakpoints of WOW64 processes as SIGINT 2020-09-24 19:01:22 +02:00
gdbsupport Tweak gdbsupport/valid-expr.h for GCC 6, fix build 2020-09-29 23:48:04 +01:00
gnulib Do not adjust mtime timezone on Windows 2020-09-08 10:41:03 -06:00
gold [GOLD] PPC64_OPT_LOCALENTRY is incompatible with tail calls 2020-09-26 20:34:55 +09:30
gprof
include Sync libiberty and include with GCC for get_DW_UT_name. 2020-09-24 22:55:24 +02:00
intl
ld PR26656 testcases 2020-09-28 19:36:35 +09:30
libctf
libdecnumber
libiberty Sync libiberty and include with GCC for get_DW_UT_name. 2020-09-24 22:55:24 +02:00
opcodes This patch introduces ETMv4 (Embedded Trace Macrocell) system registers for the AArch64 architecture. 2020-09-28 15:49:11 +01:00
readline
sim sim/m32r: return register sizes after fetch and store 2020-09-18 17:26:07 +01: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.