From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-x244.google.com (mail-pl0-x244.google.com [IPv6:2607:f8b0:400e:c01::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 40wl3N17ZFzDr5J for ; Wed, 30 May 2018 19:02:24 +1000 (AEST) Received: by mail-pl0-x244.google.com with SMTP id 30-v6so10679117pld.13 for ; Wed, 30 May 2018 02:02:23 -0700 (PDT) Date: Wed, 30 May 2018 17:02:17 +0800 From: Simon Guo To: Segher Boessenkool Cc: linuxppc-dev@lists.ozlabs.org, "Naveen N. Rao" , Cyril Bur Subject: Re: [PATCH v6 1/4] powerpc/64: Align bytes before fall back to .Lshort in powerpc64 memcmp() Message-ID: <20180530090217.GD5951@simonLocalRHEL7.x64> References: <1527221256-17029-1-git-send-email-wei.guo.simon@gmail.com> <1527221256-17029-2-git-send-email-wei.guo.simon@gmail.com> <20180528103505.GY17342@gate.crashing.org> <20180530081150.GA5951@simonLocalRHEL7.x64> <20180530082739.GF17342@gate.crashing.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20180530082739.GF17342@gate.crashing.org> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, May 30, 2018 at 03:27:39AM -0500, Segher Boessenkool wrote: > Hi! > > On Wed, May 30, 2018 at 04:11:50PM +0800, Simon Guo wrote: > > On Mon, May 28, 2018 at 05:35:12AM -0500, Segher Boessenkool wrote: > > > On Fri, May 25, 2018 at 12:07:33PM +0800, wei.guo.simon@gmail.com wrote: > > > If this doesn't use cr0 anymore, you can do rlwinm r6,r6,0,7 instead of > > > andi r6,r6,7 . > > > > > CR0 is used at .Lno_short handling. > > Tricky. > > > > > + subfc. r5,r6,r5 > > > > > > Why subfc? You don't use the carry. > > OK. I will use subfc instead. > > I meant subf -- no carry. If you want CR0 set there is subf. just fine. > > > > > + bgt cr0,8f > > > > + li r3,-1 > > > > +8: > > > > + blr > > > > > > blelr > > > li r3,-1 > > > blr > > Sure. That looks more impact. > > Should have been bgtlr of course -- well check please :-) Yes :) Thanks, - Simon