Commit 212a2676 by Richard Henderson Committed by Richard Henderson

configure.in (GCC_UNWIND_INCLUDE): Assume we're built within the same tree as gcc.

        * configure.in (GCC_UNWIND_INCLUDE): Assume we're built within
        the same tree as gcc.
        * configure: Rebuilt.

        * exception.cc (_Jv_Throw): Clarify commentary.

From-SVN: r41025
parent 847abd1f
2001-04-02 Richard Henderson <rth@redhat.com>
* configure.in (GCC_UNWIND_INCLUDE): Assume we're built within
the same tree as gcc.
* configure: Rebuilt.
* exception.cc (_Jv_Throw): Clarify commentary.
2001-04-02 Marcus G. Daniels <mgd@swarm.org>
* jni.cc (wrap_value<jclass>): New specialization.
......
......@@ -381,19 +381,8 @@ CANADIAN=no
NULL_TARGET=no
NATIVE=yes
# Find unwind.h and support headers. If we're in the tree with
# gcc, then look there. Otherwise look in compat-include. If all else
# fails, just hope the user has set things up somehow.
echo "probing $srcdir/../gcc/unwind.h"
if test -r $srcdir/../gcc/unwind.h; then
GCC_UNWIND_INCLUDE='-I$(top_srcdir)/../gcc'
else
if test -d $srcdir/../compat-include; then
GCC_UNWIND_INCLUDE='-I$(top_srcdir)/../compat-include'
else
GCC_UNWIND_INCLUDE=
fi
fi
# We're in the tree with gcc, and need to include some of its headers.
GCC_UNWIND_INCLUDE='-I$(top_srcdir)/../gcc'
if test -n "${with_cross_host}"; then
# We are being configured with a cross compiler. AC_REPLACE_FUNCS
......
......@@ -104,14 +104,13 @@ _Jv_Throw (jthrowable value)
code = _Unwind_RaiseException (&xh->unwindHeader);
#endif
/* FIXME: If code == _URC_END_OF_STACK, then we reached top of
stack without finding a handler for the exception. I seem to
recall that Java has specific rules to handle this.
If code is something else, we encountered some sort of heinous
lossage, from which we could not recover. As is the way of such
things we'll almost certainly have crashed before now, rather
than actually being able to diagnose the problem. */
/* If code == _URC_END_OF_STACK, then we reached top of stack without
finding a handler for the exception. Since each thread is run in
a try/catch, this oughtn't happen. If code is something else, we
encountered some sort of heinous lossage from which we could not
recover. As is the way of such things, almost certainly we will have
crashed before now, rather than actually being able to diagnose the
problem. */
abort ();
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment