980f45b693
Background: Originally, the EH labels were placed on the permanent obstack, which could end up using a lot of memory (for heavy inlining) since inlined labels also needed to be permanent as a result of this. This was changed in Wed Dec 9 09:12:40 1998 Andrew MacLeod <amacleod@cygnus.com> * except.h (struct handler_info): Add handler_number field. * except.c (gen_exception_label): EH labels no longer need to be on the permanent obstack. (get_new_handler): Set the label number field. (output_exception_table_entry): Regenerate handler label reference from the label number field. (init_eh): Remove a blank line. * integrate.c (get_label_from_map): Labels no longer need to be on the permanent obstack. by using the label numbers instead of the label structures in most cases. The operative word here is "most" cases. Addresses to the EH RTX was still used in (at least) flow.c, that now used freed memory. Oops. For this to happen, the freed address of the RTX representing a EH label must be reused for a new label that is located in dead code. delete_block() will then see that this RTX is mentioned in the EH table, and (incorrectly) remove the exception handler. This might be seen when, for example, compiling src/gnu/dist/groff/src/roff/troff/node.cc for m68k. |
||
---|---|---|
.. | ||
bfd | ||
binutils | ||
config | ||
contrib | ||
etc | ||
gas | ||
gcc | ||
gdb | ||
gprof | ||
include | ||
install | ||
intl | ||
ld | ||
libchill | ||
libf2c | ||
libiberty | ||
libio | ||
libobjc | ||
libstdc++ | ||
mmalloc | ||
opcodes | ||
readline | ||
sim | ||
texinfo | ||
.brik | ||
COPYING | ||
COPYING.LIB | ||
ChangeLog | ||
FAQ | ||
MAINTAINERS | ||
Makefile.in | ||
README | ||
config-ml.in | ||
config.guess | ||
config.if | ||
config.sub | ||
configure | ||
configure.in | ||
faq.html | ||
gettext.m4 | ||
install-sh | ||
libtool.m4 | ||
ltcf-c.sh | ||
ltcf-cxx.sh | ||
ltcf-gcj.sh | ||
ltconfig | ||
ltmain.sh | ||
makefile.vms | ||
md5.sum | ||
missing | ||
mkdep | ||
mkinstalldirs | ||
move-if-change | ||
mpw-README | ||
mpw-build.in | ||
mpw-config.in | ||
mpw-configure | ||
mpw-install | ||
setup.com | ||
symlink-tree | ||
ylwrap |
README
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.