From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-468153-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 15846 invoked by alias); 29 Nov 2017 12:14:05 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 15830 invoked by uid 89); 29 Nov 2017 12:14:04 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.7 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-it0-f67.google.com
Received: from mail-it0-f67.google.com (HELO mail-it0-f67.google.com) (209.85.214.67) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 29 Nov 2017 12:14:03 +0000
Received: by mail-it0-f67.google.com with SMTP id t1so3715301ite.5        for <gcc-patches@gcc.gnu.org>; Wed, 29 Nov 2017 04:14:03 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to:cc;        bh=cG+BLlPhXx2inPhN8Cnpv+h1ghH5jirzQxt2nMj9hLA=;        b=OwMhPeYhFULB2rqQ8k5EgQ+z1UIFvUGb3kWn8Z1YG637f/LszB28GmQKEA13i3gOWb         mOuHb8f9EiHNmqtBuZNuK2ZuKMf7d0cA4ip+mq5Df5JsNk7sk84SxtOcW+X313sdY01x         1wcqpOkBvfDy22aBBXq3Yl6lkElWrUp8JIMdu5shAiPVjO++BJTJXfgmdDvR3EpshsTy         g24nXb5FNxR3ztBmGMOYmvmpuoDMXhCzjHlxh82+34R4MZ++88LlMee0AnzXouOdk0+Z         x7Vtr0yhno76PU0v32IYt6o91GFC+FvW+TxNlKHAWx/Lg5aWCbJvgyfS6cZrt+Ru+IWY         5Skg==
X-Gm-Message-State: AJaThX6/HtSZUns3gWfOxBfrXX63IFv5F4T/X36TzbIuF3nkDpu3PAAn	W0lQN+wMQqZzOXYVkuDY4NSBh6x/RYeLOulIjQ4=
X-Google-Smtp-Source: AGs4zMZin/J8V00VqdivYn2E1UzvlttU8jdzkvj3H1+/Qq0t6MrOoaYOvoLGltPRYY7bgV3sj+e5mLcB9yRQ0nnvm+w=
X-Received: by 10.36.76.7 with SMTP id a7mr7119234itb.35.1511957642068; Wed, 29 Nov 2017 04:14:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.43.85 with HTTP; Wed, 29 Nov 2017 04:14:01 -0800 (PST)
In-Reply-To: <CAFULd4avvguWZVSS=mfT8KJyg1-dD0_RtPXuWCKVowiEYtUnhQ@mail.gmail.com>
References: <71475DE127B5E94A8E189586234C088822AE76FB@irsmsx105.ger.corp.intel.com> <CAFULd4avvguWZVSS=mfT8KJyg1-dD0_RtPXuWCKVowiEYtUnhQ@mail.gmail.com>
From: Uros Bizjak <ubizjak@gmail.com>
Date: Wed, 29 Nov 2017 12:38:00 -0000
Message-ID: <CAFULd4b2Nzzxkfk71Jq7aToPo5Uo=HFoATfa=YoFCDfC4sStHg@mail.gmail.com>
Subject: Re: [PATCH, i386] Fix movdi_internal to return MODE_TI with AVX512
To: "Shalnov, Sergey" <sergey.shalnov@intel.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, 	"kirill.yukhin@gmail.com" <kirill.yukhin@gmail.com>, "Koval, Julia" <julia.koval@intel.com>, 	"Senkevich, Andrew" <andrew.senkevich@intel.com>, "Peryt, Sebastian" <sebastian.peryt@intel.com>, 	"Ivchenko, Alexander" <alexander.ivchenko@intel.com>
Content-Type: text/plain; charset="UTF-8"
X-SW-Source: 2017-11/txt/msg02496.txt.bz2

On Wed, Nov 29, 2017 at 1:10 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
> On Wed, Nov 29, 2017 at 12:05 PM, Shalnov, Sergey
> <sergey.shalnov@intel.com> 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.
>
> IMO, a beter solution is to introduce ext_rex_sse_reg_operand and use
> it in place of existing ext_sse_reg_operand predicate. This is XImode
> move.

Probably you will need the same change in movsi_internal.

Uros.