From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <commeownist@yandex.ru>
Received: from forward105o.mail.yandex.net (forward105o.mail.yandex.net
 [IPv6:2a02:6b8:0:1a2d::608])
 by sourceware.org (Postfix) with ESMTPS id 50AB1385840D
 for <gcc-help@gcc.gnu.org>; Fri, 17 Sep 2021 20:52:42 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 50AB1385840D
Authentication-Results: sourceware.org;
 dmarc=pass (p=none dis=none) header.from=yandex.ru
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=yandex.ru
Received: from forward103q.mail.yandex.net (forward103q.mail.yandex.net
 [IPv6:2a02:6b8:c0e:50:0:640:b21c:d009])
 by forward105o.mail.yandex.net (Yandex) with ESMTP id 748E84C26A6
 for <gcc-help@gcc.gnu.org>; Fri, 17 Sep 2021 23:52:39 +0300 (MSK)
Received: from vla1-5c8ce23a551e.qloud-c.yandex.net
 (vla1-5c8ce23a551e.qloud-c.yandex.net
 [IPv6:2a02:6b8:c0d:400d:0:640:5c8c:e23a])
 by forward103q.mail.yandex.net (Yandex) with ESMTP id 6C92156A0002
 for <gcc-help@gcc.gnu.org>; Fri, 17 Sep 2021 23:52:39 +0300 (MSK)
Received: from vla5-3832771863b8.qloud-c.yandex.net
 (vla5-3832771863b8.qloud-c.yandex.net [2a02:6b8:c18:3417:0:640:3832:7718])
 by vla1-5c8ce23a551e.qloud-c.yandex.net (mxback/Yandex) with ESMTP id
 Y8q0s9PlbT-qdF0Qe1C; Fri, 17 Sep 2021 23:52:39 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
 t=1631911959; bh=5ypYjXfeVcE/o3touVTnAU1nClEFKZboPO4awtetDbk=;
 h=Date:To:From:Subject:Message-ID;
 b=uVFDDHCXSc3H1ZoXlIm46RAnBLkClDvX0+mTU0SRX5i6kIXefbWb+uk7EdVS03bqc
 VwT2h2uxfGqnL4zofXh6l305g+CAU4IHcrJW45aCqpoU6lJESF2ooBU0OQTaJw8YeF
 ho59RPAow6S7buH1+U9yGoUu+5VR45jwTSqYN7ko=
Authentication-Results: vla1-5c8ce23a551e.qloud-c.yandex.net;
 dkim=pass header.i=@yandex.ru
Received: by vla5-3832771863b8.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA
 id ev27e1ckdx-qc2ivOHk; Fri, 17 Sep 2021 23:52:38 +0300
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
 (Client certificate not present)
Message-ID: <c74bb06391a70fb3242af9780ac7cdb4e8254daa.camel@yandex.ru>
Subject: [QUESTION] Clobbering half of a register
From: Commeownist <commeownist@yandex.ru>
To: gcc-help@gcc.gnu.org
Date: Fri, 17 Sep 2021 23:52:13 +0300
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.40.4 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, SPF_HELO_NONE,
 SPF_PASS, TXREP autolearn=ham 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 <gcc-help.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2021 20:52:44 -0000

When specifying clobbered registers for an Extended Asm block, do
"helf-registers" clobber the whole register? For example, does adding
"ax" in the clobber list mean that GCC will treat whole "eax" (or
"rax") as clobbered?