This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[Patch, libjava] use -fnon-call-exceptions rather than -fasynchronous-unwind-tables.
- From: IainS <developer at sandoe-acoustics dot co dot uk>
- To: java-patches at gcc dot gnu dot org
- Cc: gcc patches <gcc-patches at gcc dot gnu dot org>, Richard Henderson <rth at redhat dot com>
- Date: Wed, 18 Aug 2010 10:30:46 +0100
- Subject: [Patch, libjava] use -fnon-call-exceptions rather than -fasynchronous-unwind-tables.
Hi
IIUC, the following should be the 'correct' approach.
OK for trunk? (with an appropriate changelog, of course).
Iain
Index: libjava/classpath/configure.ac
===================================================================
--- libjava/classpath/configure.ac (revision 163330)
+++ libjava/classpath/configure.ac (working copy)
@@ -563,7 +563,7 @@ if test "x${COMPILE_JNI}" = xyes; then
dnl CFLAGS that are used for all native code. We want to compile
dnl everything with unwinder data so that backtrace() will always
dnl work.
- EXTRA_CFLAGS='-fexceptions -fasynchronous-unwind-tables'
+ EXTRA_CFLAGS='-fexceptions -fnon-call-exceptions'
AC_SUBST(EXTRA_CFLAGS)
dnl Strict warning flags which not every module uses.