Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp2418348ybe; Tue, 3 Sep 2019 12:33:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqzY760QwkrZSzQvnDX90g0cP6g7WPon6jIMcabdryRlKaJPD7OqxQHUfHW9+oUlXO2Izwqi X-Received: by 2002:a63:e907:: with SMTP id i7mr31261803pgh.84.1567539185131; Tue, 03 Sep 2019 12:33:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567539185; cv=none; d=google.com; s=arc-20160816; b=atXW5CFDV7s8MhnPPPDtlbia3yZUp6GSR0t4+GQbFHBI/9skxrtCr64icSEk/oFNHz P9vL/uHj+Jhv71s5YV/gx3m//X6o09CQcZOUoDmcYcZEZHQ8+mJ/MAzq1DYVePgXOHQK v9GkkrAPlmyrUx4DDcZvB7OzdFi/4oVtTXyrqrDB7OTRZTUt1DMoMpdJw7FwzWHrAhn1 rVE4GfR4rKCQ3wVXBqotpy+oKuUrZDqFvaW9A+q5F7l6jZoFjWaY7POpMzgm+CfG6/wt X/zkzMUseE4vOkMPr1oul734P3uEBxg/CtqkXxfKOOB2yWgHRI+SpkRhS/K8rauoBtRJ 8nOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Ep49Yg6LqarOp6Q8+3UwfuTn+Y6FKAZMpwXLkLC7kp8=; b=TTH5s+ldGgdCpxp+M7s2I65IVPikZRsa2a2POVn9bWJ6FRfnwz6VdEk6DZu4htBxFX 03YP8l8eGgJEWi13bo99r7yxLk0lKjZ0OlaSOxeGlF/x1kbyw3jLEiTkvsoROY3i0RKv ydM/mg3daz5suCJrcruxtr924Wn/Drt4ffTaWKlNRwZKtr2k6bF75dhpZ38J6RRvKkku Yzl5VgvLU6xnfGDRZwoI7bIHHnGf8hO7oN6YW/bQ1R8zQqUFoe/M96lJ+djUi4KT4Cdg 5z+9FpuQrEazHJ1Dj75LmfJjoL3Uh0MPjRfbBhVKdVRu3mVlOMbD4RCTDY5BGdn01Gx8 M/5A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o61si16251095pld.132.2019.09.03.12.32.48; Tue, 03 Sep 2019 12:33:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726508AbfICTbu (ORCPT + 99 others); Tue, 3 Sep 2019 15:31:50 -0400 Received: from gate.crashing.org ([63.228.1.57]:45467 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725883AbfICTbu (ORCPT ); Tue, 3 Sep 2019 15:31:50 -0400 Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id x83JVTV8020900; Tue, 3 Sep 2019 14:31:29 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id x83JVTPO020899; Tue, 3 Sep 2019 14:31:29 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Tue, 3 Sep 2019 14:31:28 -0500 From: Segher Boessenkool To: Nathan Chancellor Cc: David Laight , Nick Desaulniers , LKML , "# 3.4.x" , clang-built-linux , Paul Mackerras , linuxppc-dev Subject: Re: [PATCH] powerpc: Avoid clang warnings around setjmp and longjmp Message-ID: <20190903193128.GC9749@gate.crashing.org> References: <20190812023214.107817-1-natechancellor@gmail.com> <878srdv206.fsf@mpe.ellerman.id.au> <20190828175322.GA121833@archlinux-threadripper> <20190828184529.GC127646@archlinux-threadripper> <6801a83ed6d54d95b87a41c57ef6e6b0@AcuMS.aculab.com> <20190903055553.GC60296@archlinux-threadripper> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190903055553.GC60296@archlinux-threadripper> User-Agent: Mutt/1.4.2.3i Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 02, 2019 at 10:55:53PM -0700, Nathan Chancellor wrote: > On Thu, Aug 29, 2019 at 09:59:48AM +0000, David Laight wrote: > > From: Nathan Chancellor > > > Sent: 28 August 2019 19:45 > > ... > > > However, I think that -fno-builtin-* would be appropriate here because > > > we are providing our own setjmp implementation, meaning clang should not > > > be trying to do anything with the builtin implementation like building a > > > declaration for it. > > > > Isn't implementing setjmp impossible unless you tell the compiler that > > you function is 'setjmp-like' ? > > No idea, PowerPC is the only architecture that does such a thing. Since setjmp can return more than once, yes, exciting things can happen if you do not tell the compiler about this. Segher