binutils-gdb modified for the FreeChainXenon project
![]() This is something I noticed while looking at ada_find_any_type. Use of that function is expensive, since it causes a global lookup. Reviewing some of the uses, I found that we were calling it to get a specific type everytime we print a tagged type (the equivalent of classes in C++); and not only that, we did it 4 times [1]! Since the type in question (ada__tags__type_specific_data) is guarantied to remain the same througout the entire life of the inferior, the solution was to cache that type in inferior private data. This patch creates an ada-land private-data area, and uses it to store that type after the first time we look it up. [1]: The problem is mitigated in AdaCore's tree because we use an Ada symbol cache which we are thinking of contributing to the FSF tree. But that's still pretty bad, regardless. 2010-05-27 Joel Brobecker <brobecker@adacore.com> * ada-lang.c (ada_inferior_data): New struct. (ada_inferior_data): New static global. (ada_inferior_data_cleanup, get_ada_inferior_data, ada_inferior_exit) (ada_get_tsd_type): New functions. (ada_tag_name_2): Use ada_get_tsd_type instead of ada_find_any_type to look the tsd type up. (_initialize_ada_language): Attach ada_inferior_exit to inferior_exit event. Set ada_inferior_data. |
||
---|---|---|
bfd | ||
binutils | ||
config | ||
cpu | ||
elfcpp | ||
etc | ||
gas | ||
gdb | ||
gold | ||
gprof | ||
include | ||
intl | ||
ld | ||
libdecnumber | ||
libiberty | ||
opcodes | ||
readline | ||
sim | ||
texinfo | ||
.cvsignore | ||
ChangeLog | ||
compile | ||
config-ml.in | ||
config.guess | ||
config.rpath | ||
config.sub | ||
configure | ||
configure.ac | ||
COPYING | ||
COPYING.LIB | ||
COPYING.LIBGLOSS | ||
COPYING.NEWLIB | ||
COPYING3 | ||
COPYING3.LIB | ||
depcomp | ||
djunpack.bat | ||
install-sh | ||
libtool.m4 | ||
ltgcc.m4 | ||
ltmain.sh | ||
ltoptions.m4 | ||
ltsugar.m4 | ||
ltversion.m4 | ||
lt~obsolete.m4 | ||
MAINTAINERS | ||
Makefile.def | ||
Makefile.in | ||
Makefile.tpl | ||
makefile.vms | ||
missing | ||
mkdep | ||
mkinstalldirs | ||
move-if-change | ||
README | ||
README-maintainer-mode | ||
setup.com | ||
src-release | ||
symlink-tree | ||
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.