public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: IainS <developer@sandoe-acoustics.co.uk>
To: java-patches@gcc.gnu.org
Cc: gcc patches <gcc-patches@gcc.gnu.org>,
	Richard Henderson <rth@redhat.com>
Subject: [Patch, libjava] use -fnon-call-exceptions rather than -fasynchronous-unwind-tables.
Date: Wed, 18 Aug 2010 09:31:00 -0000	[thread overview]
Message-ID: <6533D5F3-D5AE-475F-A309-625BC7ACBF48@sandoe-acoustics.co.uk> (raw)

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.

             reply	other threads:[~2010-08-18  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  9:31 IainS [this message]
2010-08-18  9:40 ` Richard Guenther
2010-08-18  9:45   ` Jakub Jelinek
2010-08-18 15:08     ` Richard Henderson
2010-08-18 15:15       ` Andrew Haley
2010-08-18 16:34     ` Mike Stump
2010-08-18  9:46   ` IainS
2010-08-18  9:41 ` Andrew Haley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6533D5F3-D5AE-475F-A309-625BC7ACBF48@sandoe-acoustics.co.uk \
    --to=developer@sandoe-acoustics.co.uk \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=rth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).