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 D7F263857C63 for ; Fri, 15 Jan 2021 18:52:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D7F263857C63 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 10FIpVIw008409; Fri, 15 Jan 2021 12:51:31 -0600 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 10FIpUIL008408; Fri, 15 Jan 2021 12:51:30 -0600 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Fri, 15 Jan 2021 12:51:30 -0600 From: Segher Boessenkool To: Carl Love Cc: will schmidt , Pat Haugen , GCC Patches , David Edelsohn Subject: Re: [PATCH v5] rs6000, vector integer multiply/divide/modulo instructions Message-ID: <20210115185130.GZ30983@gate.crashing.org> References: <20201119232651.GA2672@gate.crashing.org> <5d20abfbfd6e1edd7712305449e6053df8ca3043.camel@us.ibm.com> <81d86281-30d4-4d5a-b5d1-e961aa3c6573@linux.ibm.com> <20201126023036.GD2672@gate.crashing.org> <95cbf0665876f3828a6266703aa6967b089716b6.camel@us.ibm.com> <21a88b96dc4cf3d56837b3600ae57112d25db0f1.camel@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <21a88b96dc4cf3d56837b3600ae57112d25db0f1.camel@us.ibm.com> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-7.2 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: Fri, 15 Jan 2021 18:52:34 -0000 Hi! On Wed, Jan 13, 2021 at 02:15:04PM -0800, Carl Love wrote: > The patch was compiled and tested on: > > powerpc64le-unknown-linux-gnu (Power 8 BE) (I assume you mean powerpc64-linux instead?) > > Presumably it is safe (no side affects) when adding V4SI and V2DI here, > > with respect to other current users of 'bits'. > > Is it worth adding the > > other modes while we are here? (V1TI, V8HI, V16QI ). > > I did not add the additional modes. I don't see any reason it would > hurt but feel it is best to only add them when they are needed. Either works, sure. Having all but one vector modes covered is silly (and can give people the idea something is special with that one mode), but you have only two so far, so :-) > --- a/gcc/config/rs6000/rs6000.md > +++ b/gcc/config/rs6000/rs6000.md > @@ -670,7 +670,8 @@ > > ;; How many bits in this mode? > (define_mode_attr bits [(QI "8") (HI "16") (SI "32") (DI "64") > - (SF "32") (DF "64")]) > + (SF "32") (DF "64") > + (V4SI "32") (V2DI "64")]) The comment needs a clarification what this means for vector modes. "How many bits (per element) in this mode?" perhaps? Does that sound good? The patch is okay for trunk with such a tweak. Thank you! Segher