From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [IPv6:2a01:e0c:1:1599::11]) by sourceware.org (Postfix) with ESMTPS id 947873858401 for ; Sat, 8 Jan 2022 14:42:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 947873858401 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=libertysurf.fr Authentication-Results: sourceware.org; spf=none smtp.mailfrom=libertysurf.fr Received: from fomalhaut.localnet (unknown [IPv6:2a01:e0a:41b:84f0:cf71:f5e0:b050:bede]) by smtp2-g21.free.fr (Postfix) with ESMTP id B2DE920039E; Sat, 8 Jan 2022 15:42:06 +0100 (CET) From: Eric Botcazou To: Martin Uecker Cc: Richard Biener , "gcc@gcc.gnu.org" Subject: Re: reordering of trapping operations and volatile Date: Sat, 08 Jan 2022 15:41:56 +0100 Message-ID: <5784303.lOV4Wx5bFT@fomalhaut> In-Reply-To: <30b077c2231d31e0fb345584adef27ebe233c418.camel@gmail.com> References: <832b1b3957a0243ca37378a774effe537642eed3.camel@gmail.com> <5D6DA24A-954F-43C0-960F-54FE176D0607@gmail.com> <30b077c2231d31e0fb345584adef27ebe233c418.camel@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_NONE, 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@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2022 14:42:11 -0000 > Yes, although I think potentially trapping ops > are not moved before calls (as this would be > incorrect). So do you think it would be feasable > to prevent this for volatile too? Feasible probably, but why would this be desirable in C? It's not Java! -- Eric Botcazou