From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by sourceware.org (Postfix) with ESMTP id 402B23861812 for ; Fri, 10 Sep 2021 18:37:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 402B23861812 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=kernel.crashing.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=kernel.crashing.org Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 18AIaAYk016599; Fri, 10 Sep 2021 13:36:10 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 18AIaArO016598; Fri, 10 Sep 2021 13:36:10 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Fri, 10 Sep 2021 13:36:09 -0500 From: Segher Boessenkool To: HON LUU Cc: "gcc-help@gcc.gnu.org" Subject: Re: gcc question Message-ID: <20210910183609.GA1583@gate.crashing.org> References: <20210908162025.GO1583@gate.crashing.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2021 18:37:19 -0000 On Fri, Sep 10, 2021 at 05:58:07PM +0000, HON LUU wrote: > Hi Segher, > > I wonder if you have any issues to reproduce the problem. > Attached is the tar ball of stand alone module, which duplicate the issue. > There is a README file, should be straightforward to duplicate the issue. > You need to show the full code of the asm_volatile_goto, and the declarations of everything used in its operands, for us to get a handle on what is going on here. Bonus points if you manage to make a stand- alone compilable testcase that shows the problem. If you write up a good email with all the necessary info, you will get an answer (and a good answer!) much quicker. I do not particularly feel like doing all the work here. Sorry. Segher