From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 123019 invoked by alias); 13 Apr 2016 13:45:22 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 122988 invoked by uid 89); 13 Apr 2016 13:45:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=HX-Gm-Message-State:AOPr4FX, H*MI:sk:2016041 X-HELO: mail-wm0-f68.google.com Received: from mail-wm0-f68.google.com (HELO mail-wm0-f68.google.com) (74.125.82.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 13 Apr 2016 13:45:20 +0000 Received: by mail-wm0-f68.google.com with SMTP id l6so14123116wml.3 for ; Wed, 13 Apr 2016 06:45:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=xkAueLSob55GmD1aXPEcSZtXLTgi+X4BQFvrGBc/7jE=; b=FbZ88oVlV0oFTYusG1zV5kH4V/fmV5qbED7Pd0DV4OOaiJLwDQHVLJDsJSouyzuyor Qbkh320aCsTcU3dwjss+hwHwYiLM7NpKyJJzIsV8qj0vk+KdEsoBwqX7cpGjox9Bf3dl 6WUhcAKy+tX1P3AjMgm02/uz7tAdUuhC/r2i5Zgm8AfETRoLfEMcrXujti/PTelKQMxc aR7aU4Tftu1jdzp8OXP19+gjrc+CraK5RsWiMj4N/yRx0uUqbuAUa6FuDcXEjvXrbUZN oui4FlNpuKegSBC0mcVuprPq4Ri5Q2yneyPhDzVlYXfBmcUqLerROVYiS83LIb9WKHy8 +Oqg== X-Gm-Message-State: AOPr4FX/MzxkaP9rHNCcbJah46t3lj89hd8Z4s7r1gkS2+hyQftzQEjxSUJTCsfsHJYumA== X-Received: by 10.28.130.133 with SMTP id e127mr24283296wmd.48.1460555117277; Wed, 13 Apr 2016 06:45:17 -0700 (PDT) Received: from msticlxl57.ims.intel.com (irdmzpr02-ext.ir.intel.com. [192.198.151.37]) by smtp.gmail.com with ESMTPSA id u145sm1358611wmu.17.2016.04.13.06.45.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Apr 2016 06:45:16 -0700 (PDT) Date: Wed, 13 Apr 2016 13:45:00 -0000 From: Kirill Yukhin To: Ilya Enkovich Cc: gcc-patches@gcc.gnu.org, ubizjak@gmail.com; Subject: Re: [PATCH, i386] Fix operands order in kunpck* insns and corresponding expands Message-ID: <20160413134409.GA36029@msticlxl57.ims.intel.com> References: <20160413132956.GA13305@msticlxl57.ims.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160413132956.GA13305@msticlxl57.ims.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-IsSubscribed: yes X-SW-Source: 2016-04/txt/msg00580.txt.bz2 Hi Ilya, On 13 Apr 16:29, Ilya Enkovich wrote: > Hi, > > Current kunpck[hi|si|di] patterns emit operands in a wrong order. This > is compensated by a wrong operands order in vec_pack_trunc_[qi|hi|si] > expands and therefore we get correct code for vectorized loops. Code > using kunpck* intrinsics would be wrong though. This patch fixes > operands order and adds runtime tests for _mm512_kunpack* intrinsics. > > Bootstrapped and regtested on x86_64-pc-linux-gnu. OK for trunk? Patch is OK. > > Thanks, > Ilya -- Thanks, K