From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30809 invoked from network); 13 Aug 2020 08:54:13 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 13 Aug 2020 08:54:13 -0000 Received: (qmail 9694 invoked by uid 550); 13 Aug 2020 08:54:10 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 9673 invoked from network); 13 Aug 2020 08:54:10 -0000 Date: Thu, 13 Aug 2020 11:53:58 +0300 (MSK) From: Alexander Monakov To: musl@lists.openwall.com In-Reply-To: <20200813100120.5bb689e8@inria.fr> Message-ID: References: <20200811181116.8433-1-amonakov@ispras.ru> <20200811184527.GM3265@brightrain.aerifal.cx> <20200813100120.5bb689e8@inria.fr> User-Agent: Alpine 2.20.13 (LNX 116 2015-12-14) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Subject: Re: [musl] [PATCH 1/3] setjmp: fix x86-64 longjmp argument adjustment On Thu, 13 Aug 2020, Jens Gustedt wrote: > Alexander, > probably this has nothing to do with the issue at hand but > > on Wed, 12 Aug 2020 16:29:59 +0300 (MSK) you (Alexander Monakov > ) wrote: > > > int v = setjmp(jb); > > is a use of `setjmp` that is not conforming. `setjmp` is only allowed > either standalone or as controlling expression either directly or > negated. Thanks. Yeah, this is a moot point as the test needs GCC with -O anyway, and GCC allows setjmp in any context. But nevertheless it's easy to adjust it by changing the offending line to 'if (setjmp(jb)) return 0;' and changing the final 'return !v' to 'return 1'. Alexander