DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=EM6zzIBGVgw/4vE2/sMXCLpeedg+v
	fWaeh0EoLsZoV5m2Sy1lo16xSpML3qimQVDaFGQe0C9sJgVbrvxuiE/vZjw5lqnK
	4STqmxYqnelSxgwNV3XGl5BYu1XiZtZlQ3FJ6Aaq4G3wheddqTu5y6J3BWWuMj/D
	Ww/jlQJdRV/bbI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Schwarz, Konrad" <konrad.schwarz@siemens.com>
To: Eric Blake <eblake@redhat.com>,
        The Cygwin Mailing List	<cygwin@cygwin.com>,
        "newlib@sourceware.org" <newlib@sourceware.org>
Subject: RE: allowing redefinition of setjmp()?
Date: Mon, 26 Jan 2015 10:19:28 +0000
Message-ID: <A45B1767F1002449A37508C2CC6003D707556F@DEFTHW99EJ1MSX.ww902.siemens.net>
References: <54C2C68E.5090100@redhat.com>
In-Reply-To: <54C2C68E.5090100@redhat.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

> -----Original Message-----
> To: The Cygwin Mailing List; newlib@sourceware.org
> Subject: allowing redefinition of setjmp()?
> Reading POSIX, I see that Cygwin is compliant, and readline is at
> fault.
>  http://pubs.opengroup.org/onlinepubs/9699919799/functions/setjmp.html
> is clear:
> 
> "It is unspecified whether setjmp() is a macro or a function. If a
> macro definition is suppressed in order to access an actual function,
> or a program defines an external identifier with the name setjmp, the
> behavior is undefined."

Honestly, this is what I expected.

> But as the redefine works in Linux, I'm wondering if we tweak things in
> Cygwin and/or newlib to allow it to work here too.  Maybe by making an
> entry point __setjmp() as an alias for setjmp(), and defining
> sigsetjmp() in terms of __setjmp(), so that when someone adds a #define
> wrapper for setjmp, it is no longer a mutually recursive macro naming
> scenario.

It this really worth it?

> In the meantime, I'm resorting to patching up readline code to quit
> trying to (re)define setjmp.

Stating the obvious, all you need to do is globally replace setjmp() with e.g. readline_setjmp().