public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	"libstdc++" <libstdc++@gcc.gnu.org>,
		Java Patch List <java-patches@gcc.gnu.org>
Subject: Re: [patch] Clean up detection of SJLJ exceptions in target libraries
Date: Wed, 13 May 2015 07:55:00 -0000	[thread overview]
Message-ID: <CA+=Sn1k+_XKRsun+D7kEZg-vEWx-_Bppdhhf41G2_B6uzKiF=A@mail.gmail.com> (raw)
In-Reply-To: <1440100.16fMh0Bpp2@polaris>

On Tue, May 12, 2015 at 9:42 AM, Eric Botcazou <ebotcazou@adacore.com> wrote:
> Hi,
>
> 6 target libraries in the tree detect whether they are being compiled by a
> compiler configured for setjmp/longjmp exceptions: libada, libgcc, libgo,
> libjava, libobjc and libstdc++.  They can be divided into 3 categories:
>  1) libada only checks the preprocessor macro __USING_SJLJ_EXCEPTIONS__,
>  2) libgcc and libgo both check the preprocessor macro and implement a
> configure check that defines another macro (LIBGCC_SJLJ_EXCEPTIONS and
> LIBGO_SJLJ_EXCEPTIONS resp) so they'd better agree.
>  3) libjava, libobjc and libstdc++ implement a configure check that defines a
> macro (SJLJ_EXCEPTIONS, SJLJ_EXCEPTIONS and _GLIBCXX_SJLJ_EXCEPTIONS resp).
>
> The attached patch gets rid of the library-specific macros and replaces them
> with __USING_SJLJ_EXCEPTIONS__.  Moreover, it adds a config/sjlj.m4 fragment
> that defines GCC_CHECK_SJLJ_EXCEPTIONS for libraries that need to detect the
> exception model in the configure phase (libgcc and libjava only).
>
> Tested on x86_64-suse-linux with --enable-sjlj-exceptions.  The results are
> not clean (except for objc and obj-c++) but sufficient to see that exceptions
> still work after the patch.  OK for the mainline?
>
>
> 2015-05-12  Eric Botcazou  <ebotcazou@adacore.com>
>
> config/
>         * sjlj.m4: New file.
>
> libgcc/
>         * configure.ac: Include config/sjlj.m4.
>         Remove manual SJLJ check, add GCC_CHECK_SJLJ_EXCEPTIONS and adjust.
>         * config.in: Regenerate.
>         * configure: Likewise.
>         * config.host: Replace enable_sjlj_exceptions by ac_cv_sjlj_exceptions.
>
> libgo/
>         * configure.ac: Remove manual SJLJ check.
>         * config.h.in: Regenerate.
>         * configure: Likewise.
>         * runtime/go-unwind.c: Replace LIBGO_SJLJ_EXCEPTIONS by
>         __USING_SJLJ_EXCEPTIONS__.
>
> libjava/
>         * configure.ac: Include config/sjlj.m4.
>         Remove manual SJLJ check, add GCC_CHECK_SJLJ_EXCEPTIONS and adjust.
>         * include/config.h.in: Regenerate.
>         * configure: Likewise.
>         * exception.cc: Replace SJLJ_EXCEPTIONS by __USING_SJLJ_EXCEPTIONS__.
>         * stacktrace.cc: Likewise.
>         * include/default-signal.h: Likewise.
>         * sysdep/i386/backtrace.h: Likewise.
>
> libobjc/
>         * configure.ac: Remove manual SJLJ check.
>         * config.h.in: Regenerate.
>         * configure: Likewise.
>         * exception.c: Replace SJLJ_EXCEPTIONS by __USING_SJLJ_EXCEPTIONS__.


The libobjc parts are ok.

Thanks,
Andrew Pinski

>
> libstdc++-v3/
>         * acinclude.m4 (GLIBCXX_ENABLE_SJLJ_EXCEPTIONS): Delete.
>         * configure.ac: Remove GLIBCXX_ENABLE_SJLJ_EXCEPTIONS.
>         * config.h.in: Regenerate.
>         * configure: Likewise.
>         * libsupc++/eh_personality.cc: Replace _GLIBCXX_SJLJ_EXCEPTIONS by
>         __USING_SJLJ_EXCEPTIONS__.
>         * libsupc++/eh_throw.cc: Likewise.
>         * libsupc++/eh_ptr.cc: Likewise.
>         * doc/html/manual/appendix_porting.html: Remove
>         GLIBCXX_ENABLE_SJLJ_EXCEPTIONS
>         * doc/xml/manual/build_hacking.xml: Likewise.
>         * doc/html/manual/configure.html: Remove --enable-sjlj-exceptions.
>         * doc/xml/manual/configure.xml: Likewise.
>
>
> --
> Eric Botcazou

  parent reply	other threads:[~2015-05-13  7:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 16:45 Eric Botcazou
2015-05-12 20:26 ` Jeff Law
2015-05-13  7:53   ` Eric Botcazou
2015-05-13  7:55 ` Andrew Pinski [this message]
2015-05-13 10:37 ` Jonathan Wakely
2015-05-13 12:11   ` Matt Breedlove
2015-05-13 16:11     ` Eric Botcazou
2015-05-13 16:26 ` Ian Lance Taylor
2015-05-13 17:53   ` Eric Botcazou

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='CA+=Sn1k+_XKRsun+D7kEZg-vEWx-_Bppdhhf41G2_B6uzKiF=A@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    /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).