From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 624693858005 for ; Wed, 21 Dec 2022 22:46:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 624693858005 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1671662787; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XtyDkYy7o0LzUPivuneVhsfgbTwBrAD+ETAaQGqLyy8=; b=bnGVRuvnqsgmNX2MtUuo4u6UDZBt2SupCQUiDVXyS5JL4f/QLCt6yuohZdsIabud+3YS6t +uoqIxekWDzA6YQhGtQBJVSNB/wPCcRvBi35Or0OZWmWfh1tvxViiY/FCR4sOU1iYxEj7q TNvbIO4/lbFg7Pu25ldsoXNlQX9YqU8= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-413-BeUOMe6nMo-Mr0zfESZZLQ-1; Wed, 21 Dec 2022 17:46:23 -0500 X-MC-Unique: BeUOMe6nMo-Mr0zfESZZLQ-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3318B887407; Wed, 21 Dec 2022 22:46:23 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.195.114]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D31501731B; Wed, 21 Dec 2022 22:46:22 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 2BLMkKjg3276628 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Wed, 21 Dec 2022 23:46:20 +0100 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 2BLMkJwL3276627; Wed, 21 Dec 2022 23:46:19 +0100 Date: Wed, 21 Dec 2022 23:46:18 +0100 From: Jakub Jelinek To: "H.J. Lu" Cc: Hongtao Liu , liuhongt , gcc-patches@gcc.gnu.org, ubizjak@gmail.com Subject: Re: [PATCH V2 2/2] [x86] x86: Add a new option -mdaz-ftz to enable FTZ and DAZ flags in MXCSR. Message-ID: Reply-To: Jakub Jelinek References: <20221215062137.3128845-1-hongtao.liu@intel.com> <20221215062137.3128845-2-hongtao.liu@intel.com> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,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: On Wed, Dec 21, 2022 at 02:43:43PM -0800, H.J. Lu wrote: > > > > > > > Target RejectNegative > > > > > > > Set 80387 floating-point precision to 80-bit. > > > > > > > > > > > > > > +mdaz-ftz > > > > > > > +Target > > > > > > > > > > > > s/Target/Driver/ > > > > > Change to Driver and Got error like:cc1: error: command-line option > > > > > ‘-mdaz-ftz’ is valid for the driver but not for C. > > > > Hi Jakub: > > > > I didn't find a good solution to handle this error after changing > > > > *Target* to *Driver*, Could you give some hints how to solve this > > > > problem? > > > > Or is it ok for you to mark this as *Target*(there won't be any save > > > > and restore in cfun since there's no variable defined here.) > > > > > > Since all -m* options are passed to cc1, -mdaz-ftz can't be marked > > > as Driver. We need to give it a different name to mark it as Driver. > > > > It is ok like that. > > > > Jakub > > > > The GCC driver handles -mno-XXX automatically for -mXXX. Use > a different name needs to handle the negation. Or we can do something > like this to check for CL_DRIVER before passing it to cc1. I meant I'm ok with -m{,no-}daz-ftz option being Target rather than Driver. Jakub