public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Remove SETJMP_VIA_SAVE_AREA support
Date: Fri, 10 Jun 2011 03:52:00 -0000	[thread overview]
Message-ID: <alpine.BSF.2.00.1106092315430.61896@dair.pair.com> (raw)
In-Reply-To: <201106091437.43102.ebotcazou@adacore.com>

On Thu, 9 Jun 2011, Eric Botcazou wrote:
> > Poison it (in system.h)?
>
> Let's keep pretending that it never existed. :-)

No can do.  It had been there for too many releases (even one is
one too many), at least 13 years according to the ChangeLogs.
I even went looking for it for PR48542 having a vague
recollection of it.  Committed as obvious.

gcc:
	* system.h (SETJMP_VIA_SAVE_AREA): Poison.

Index: system.h
===================================================================
--- system.h	(revision 174865)
+++ system.h	(working copy)
@@ -826,7 +826,8 @@ extern void fancy_abort (const char *, i
 	FUNCTION_ARG_BOUNDARY MUST_USE_SJLJ_EXCEPTIONS US_SOFTWARE_GOFAST  \
 	USING_SVR4_H SVR4_ASM_SPEC FUNCTION_ARG FUNCTION_ARG_ADVANCE	   \
 	FUNCTION_INCOMING_ARG IRA_COVER_CLASSES TARGET_VERSION		   \
-	MACHINE_TYPE TARGET_HAS_TARGETCM ASM_OUTPUT_BSS
+	MACHINE_TYPE TARGET_HAS_TARGETCM ASM_OUTPUT_BSS			   \
+	SETJMP_VIA_SAVE_AREA

 /* Hooks that are no longer used.  */
  #pragma GCC poison LANG_HOOKS_FUNCTION_MARK LANG_HOOKS_FUNCTION_FREE	\

brgds, H-P

  reply	other threads:[~2011-06-10  3:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 10:49 Eric Botcazou
2011-06-02 21:53 ` Eric Botcazou
2011-06-09  7:15 ` Hans-Peter Nilsson
2011-06-09 13:06   ` Eric Botcazou
2011-06-10  3:52     ` Hans-Peter Nilsson [this message]
2011-06-10  7:19       ` Eric Botcazou
2012-04-18 19:19 ` Mike Stump
2012-04-23 10:06   ` 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=alpine.BSF.2.00.1106092315430.61896@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=ebotcazou@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).