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 48A00385DC2E for ; Wed, 30 Sep 2020 20:13:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 48A00385DC2E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=kernel.crashing.org Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=segher@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 08UKC5KG001082; Wed, 30 Sep 2020 15:12:05 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 08UKC4XX001081; Wed, 30 Sep 2020 15:12:04 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Wed, 30 Sep 2020 15:12:04 -0500 From: Segher Boessenkool To: Richard Biener Cc: gcc-patches@gcc.gnu.org, joseph@codesourcery.com, ". Jakub Jelinek" , Richard Sandiford Subject: Re: [PATCH v2] builtins: (not just) rs6000: Add builtins for fegetround, feclearexcept and feraiseexcept [PR94193] Message-ID: <20200930201204.GZ28786@gate.crashing.org> References: <20200904155230.nyssphhldu47hbve@work-tp> <20200929233806.GW28786@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=-7.1 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, TXREP, T_SPF_HELO_PERMERROR, T_SPF_PERMERROR autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2020 20:13:13 -0000 On Wed, Sep 30, 2020 at 09:02:34AM +0200, Richard Biener wrote: > On Tue, 29 Sep 2020, Segher Boessenkool wrote: > > I don't see much about optabs in the docs either. Add some text to > > optabs.def itself then? > > All optabs are documented in doc/md.texi as 'instruction patterns' Except for what seems to be the majority that isn't. > This is where new optabs need to be documented. It's going to be challenging to find a reasonable spot in there. Oh well. Thanks, Segher