From patchwork Wed Aug 18 09:30:46 2010
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [libjava] use -fnon-call-exceptions rather than
 -fasynchronous-unwind-tables.
Date: Tue, 17 Aug 2010 23:30:46 -0000
From: IainS <developer@sandoe-acoustics.co.uk>
X-Patchwork-Id: 62015
Message-Id: <6533D5F3-D5AE-475F-A309-625BC7ACBF48@sandoe-acoustics.co.uk>
To: java-patches@gcc.gnu.org
Cc: gcc patches <gcc-patches@gcc.gnu.org>, Richard Henderson <rth@redhat.com>

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.