2
0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2024-12-21 04:42:53 +08:00
Go to file
Weimin Pan 844be3f240 CTF: set up debug info for function arguments
Added this support in read_func_kind_type after gcc started generating
CTF for function arguments.

Replaced XNEW with std::vector and NULL with nullptr.

Expanded gdb.base/ctf-ptype.exp to test function arguments. Also fixed
some typos.

gdb/ChangeLog:

	* ctfread.c (read_func_kind_type): Set up function arguments.

gdb/testsuite/ChangeLog:

	* gdb.base/ctf-ptype.exp: Add function tests and fix typos.
2021-03-05 20:46:39 -05:00
bfd Automatic date update in version.in 2021-03-06 00:00:16 +00:00
binutils bfd/binutils: add support for RISC-V CSRs in core files 2021-03-05 17:21:41 +00:00
config config/debuginfod: do not include pkg.m4 directly 2021-02-13 00:15:11 -05:00
contrib
cpu
elfcpp
etc
gas Correct an error message in the ARM assembler. 2021-02-26 16:37:30 +00:00
gdb CTF: set up debug info for function arguments 2021-03-05 20:46:39 -05:00
gdbserver gdbserver: linux-low: make linux_process_target::filter_event return void 2021-02-23 10:56:56 -05:00
gdbsupport
gnulib
gold
gprof
include bfd/binutils: add support for RISC-V CSRs in core files 2021-03-05 17:21:41 +00:00
intl intl: turn LIBINTL into -L / -l form 2021-02-10 15:26:57 +00:00
ld ld: adjust ld-scripts/map-address.* 2021-03-04 16:56:40 +01:00
libctf bfd, ld, libctf: skip zero-refcount strings in CTF string reporting 2021-03-02 15:10:10 +00:00
libdecnumber
libiberty
opcodes x86: infer operand count of templates 2021-03-03 12:57:08 +01:00
readline Fix Readline 8.1 build on mingw 2021-03-02 13:42:37 -07:00
sim sim: igen: drop config.h & header checking 2021-02-28 03:32:47 -05:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ar-lib
ChangeLog Add missing changes to Makefile.tpl 2021-02-28 04:39:38 -08:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure Remove arm-symbianelf 2021-02-09 23:36:16 +10:30
configure.ac Remove arm-symbianelf 2021-02-09 23:36:16 +10:30
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 Add missing changes to Makefile.tpl 2021-02-28 04:39:38 -08:00
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.