From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29949 invoked by alias); 1 Dec 2017 06:44:43 -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 29939 invoked by uid 89); 1 Dec 2017 06:44:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_NUMSUBJECT,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy= X-HELO: mail-wm0-f65.google.com Received: from mail-wm0-f65.google.com (HELO mail-wm0-f65.google.com) (74.125.82.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 01 Dec 2017 06:44:41 +0000 Received: by mail-wm0-f65.google.com with SMTP id r78so1640577wme.5 for ; Thu, 30 Nov 2017 22:44:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=7pultcUYNKmdrSlf12jd5VpuXWrA7lWGO6kF6GmvbxU=; b=cdtWK7jJ7NmdK859cvASGz+SqxWmE8CcaEdVMcFKO+ZYPXeg1gijBFN+zv110q4lq9 1pAN4T7UBsyOuL7v+Nts10fJVSeY3HDltohfTwmfUqbsoQIjPFMwWowPyR1hPsC8R3To jZ9xNzvWxg4Ojw3vKHPutlfTR9uik/Gn/BXqyQ9FBNmlpHmUw1RxBmu+m+fT3bD7D3mP CH6BgWjlCJ9xWOVVjm9kD8gDT1hCnKv7zVxjtIXQ0kjsryo2Qqwgw4sizvdJFQBRME4K di9FwkCI54tx5sSrppOL9ipGC7PrzoxdO296l6G5yQ3rnquYeXVOb9eml4RDttLi2L0a 2Log== X-Gm-Message-State: AJaThX46thFQ85kxTGQiBQIqnaqX+9cZJ/A9dtEDcaj8Sf665kH97ezu Wg+Jj4FUoxWR1icyCRu6Rzo= X-Google-Smtp-Source: AGs4zMbnwE27uS7sKVgWAhnL4pBpUhXLM9C3CqsXezvstkkqP5WSf5rMXmGo9WlFkZ1gbLTu5kFVLA== X-Received: by 10.80.231.7 with SMTP id a7mr15815000edn.268.1512110679130; Thu, 30 Nov 2017 22:44:39 -0800 (PST) Received: from titus (95-26-13-8.broadband.corbina.ru. [95.26.13.8]) by smtp.gmail.com with ESMTPSA id v15sm4116126edb.41.2017.11.30.22.44.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Nov 2017 22:44:38 -0800 (PST) Date: Fri, 01 Dec 2017 06:44:00 -0000 From: Kirill Yukhin To: "Shalnov, Sergey" Cc: "'gcc-patches@gcc.gnu.org'" , "Koval, Julia" , "Senkevich, Andrew" , "Peryt, Sebastian" , "Ivchenko, Alexander" , 'Uros Bizjak' Subject: Re: [PATCH, i386] Fix movdi_internal to return MODE_TI with AVX512 Message-ID: <20171201064429.GE22657@titus> References: <71475DE127B5E94A8E189586234C088822AE76FB@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <71475DE127B5E94A8E189586234C088822AE76FB@irsmsx105.ger.corp.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-IsSubscribed: yes X-SW-Source: 2017-12/txt/msg00017.txt.bz2 Hello Sergey, On 29 Nov 11:05, Shalnov, Sergey wrote: > Hi, > I found wrong MODE_XI used in movdi_internal that cause zmm > Generation with "-march=skylake-avx512 -mprefer-vector-width=128" > options set. This patch fixes the mode and register type but keep using > AVX512 instruction set. > > 2017-11-28 Sergey Shalnov > gcc/ > * config/i386/i386.md: Fix AVX512 register width > in AVX512 instruction. Your patch is OK. I've checked it into main trunk. -- Thanks, K