From: Eric Botcazou <botcazou@adacore.com>
To: gcc-patches@gcc.gnu.org
Subject: Repair --disable-sjlj-exceptions
Date: Sat, 29 Oct 2022 14:14:23 +0200 [thread overview]
Message-ID: <21653628.EfDdHjke4D@fomalhaut> (raw)
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
It was broken by:
2022-08-31 Martin Liska <mliska@suse.cz>
* config.build: Remove deprecated ports.
* config.gcc: Likewise.
* config.host: Likewise.
* configure.ac: Likewise.
* configure: Regenerate.
* config/pa/pa-hpux10.h: Removed.
* config/pa/pa-hpux10.opt: Removed.
* config/pa/t-dce-thr: Removed.
Tested by building i686-w64-mingw32 with --disable-sjlj-exceptions, applied on
the mainline as obvious.
2022-10-29 Eric Botcazou <ebotcazou@adacore.com>
* configure.ac (sjlj-exceptions): Restore dropped line.
* configure: Regenerate.
--
Eric Botcazou
[-- Attachment #2: p.diff --]
[-- Type: text/x-patch, Size: 414 bytes --]
diff --git a/gcc/configure.ac b/gcc/configure.ac
index eb92a37cd46..4ecccffc324 100644
--- a/gcc/configure.ac
+++ b/gcc/configure.ac
@@ -1805,6 +1805,7 @@ AC_SUBST(objext)
AC_ARG_ENABLE(sjlj-exceptions,
[AS_HELP_STRING([--enable-sjlj-exceptions],
[arrange to use setjmp/longjmp exception handling])],
+[force_sjlj_exceptions=yes],
[case $target in
lm32*-*-*)
force_sjlj_exceptions=yes
reply other threads:[~2022-10-29 12:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=21653628.EfDdHjke4D@fomalhaut \
--to=botcazou@adacore.com \
--cc=gcc-patches@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).