From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cc-smtpout1.netcologne.de (cc-smtpout1.netcologne.de [89.1.8.211]) by sourceware.org (Postfix) with ESMTPS id BCB313858D37; Wed, 21 Sep 2022 09:58:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org BCB313858D37 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=netcologne.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=netcologne.de Received: from cc-smtpin1.netcologne.de (cc-smtpin1.netcologne.de [89.1.8.201]) by cc-smtpout1.netcologne.de (Postfix) with ESMTP id C489E1221F; Wed, 21 Sep 2022 11:57:59 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1663754279; bh=zNSiDOdohceSVxt/NeTH6v78gfeKbsZBcZWR/XpHrLU=; h=Message-ID:Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Z702XMNkwqfBtj+pxBQtokNJA0JofrdohGIxb/c8s1bLvditI34B0uJx5/U3mBw5m pUfeZ79vaSAR/UNbcgvsHfoTTRoWdnKsjRgUUB5E95adrx/x7tOdqngTYGTikz67SC fJZm5Wvo1p5KRyUt1THqmLPcEBV7bTJ/wZZ7G2MsQSIoGRaUhCSpCN9+iesMCiUJBT hs72pDC0gvnmMvvvCkceD3jhKn7673fyC78hNdLY4HLuQv4sZYuU4wNYHN3DO/xiPX YrHAwcilTjy2HIxuY6kxc4Nh6bDGJGBLLZvKTGGXR7NRuTuINfC0kGBXjuY6roRs4A 0q6tpRcSdywtA== Received: from [IPV6:2001:4dd7:1257:0:7285:c2ff:fe6c:992d] (2001-4dd7-1257-0-7285-c2ff-fe6c-992d.ipv6dyn.netcologne.de [IPv6:2001:4dd7:1257:0:7285:c2ff:fe6c:992d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by cc-smtpin1.netcologne.de (Postfix) with ESMTPSA id E842411D91; Wed, 21 Sep 2022 11:57:54 +0200 (CEST) Message-ID: Date: Wed, 21 Sep 2022 11:57:54 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PATCH 09/10] fortran: Support clobbering of variable subreferences [PR88364] Content-Language: en-US To: Harald Anlauf , Mikael Morin , Richard Biener Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org References: <20220916202439.549820-1-mikael@gcc.gnu.org> <20220916202439.549820-10-mikael@gcc.gnu.org> <3edab734-f5bb-5557-ff98-b0ce47d7c510@orange.fr> <3ef8c5c4-35a1-fa60-2a2d-a7bb3fbd35fc@gmx.de> <9996bd59-9cf1-12df-faa5-7d546e5732f7@orange.fr> <6ac60050-2298-df01-1345-d53c868ed5d9@gmx.de> <0a36f845-13fb-5046-7731-87f4832e8deb@orange.fr> From: Thomas Koenig In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-NetCologne-Spam: L X-Rspamd-Queue-Id: E842411D91 X-Spamd-Bar: / X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Harald, > I think I understand much of what is said, but I feel that I do > not really understand what *clobber* means for the different > beasts we are discussing (although I have an impression of what > it means for a scalar object). Obviously, "clobber" means taking a big stick and hitting the beast in question over the head with it :-) More seriously: My understanding of a clobber it is a hint to the middle end that the value in question will not be used, and that operations leading to this value can be removed, unless they are used otherwise. If I'm wrong or imprecise, I'm sure somebody will correct me :-) Regards Thomas