Go to file
Andrew Burgess 2c75ccb24c gdb: avoid accessing global C++ language implementation functions
The function c_printchar is called from two places; it provides the
implementation of language_defn::printchar and it is called from
dwarf2_compute_name.

It would be nice to rename c_printchar as language_defn::printchar and
so avoid the trampoline.

To achieve this, instead of calling c_printchar directly from the
DWARF code, I lookup the C++ language object and call the printchar
member function.

In a later commit I can then rename c_printchar.

There should be no user visible changes after this commit.

gdb/ChangeLog:

	* dwarf2/read.c (dwarf2_compute_name): Call methods on C++
	language object instead of calling global functions directly.
2020-12-23 20:53:14 +00:00
bfd Automatic date update in version.in 2020-12-23 00:00:06 +00:00
binutils Handle DT_GNU_FLAGS_1 in readelf 2020-12-15 18:45:09 +10:30
config
contrib
cpu
elfcpp Cosmetic improvements for OSABI access. 2020-12-15 14:37:22 -08:00
etc
gas Statically initialise target common sections 2020-12-18 10:34:16 +10:30
gdb gdb: avoid accessing global C++ language implementation functions 2020-12-23 20:53:14 +00:00
gdbserver Fix TBI handling for watchpoints 2020-12-16 10:05:56 -03:00
gdbsupport gdbsupport: make use of safe-ctype functions from libiberty 2020-12-11 22:04:28 +00:00
gnulib
gold gold: Move sym declaration just before use 2020-12-19 13:37:04 -08:00
gprof
include Assorted tidies 2020-12-18 10:34:16 +10:30
intl
ld ld: Build and install only unversioned libdep 2020-12-18 04:30:59 -08:00
libctf libctf: Pass format argument to asprintf 2020-11-25 19:11:36 +00:00
libdecnumber
libiberty
opcodes RISC-V: Add sext.[bh] and zext.[bhw] pseudo instructions. 2020-12-10 10:50:44 +08:00
readline
sim Add support for the SDIV and UDIV instructions to the ARM simulator. 2020-12-15 12:40:35 +00:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore Add gnu global outputs to .gitignore 2020-12-02 10:00:27 -05:00
ar-lib
ChangeLog [gdb] Print progress for debuginfod 2020-12-16 18:18:40 +01:00
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 Use sha256 for hashes in the release process 2020-10-28 10:35:28 -04: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.