From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-335287-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 20526 invoked by alias); 10 Jan 2013 11:28:32 -0000
Received: (qmail 20517 invoked by uid 22791); 10 Jan 2013 11:28:31 -0000
X-SWARE-Spam-Status: No, hits=-5.0 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
Received: from mail-oa0-f48.google.com (HELO mail-oa0-f48.google.com) (209.85.219.48)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 10 Jan 2013 11:28:25 +0000
Received: by mail-oa0-f48.google.com with SMTP id h2so420321oag.35        for <gcc-patches@gcc.gnu.org>; Thu, 10 Jan 2013 03:28:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.212.70 with SMTP id ni6mr51584324obc.44.1357817304306; Thu, 10 Jan 2013 03:28:24 -0800 (PST)
Received: by 10.182.153.201 with HTTP; Thu, 10 Jan 2013 03:28:24 -0800 (PST)
In-Reply-To: <CAK1BsWoJvbcu_icjUoXKs4dkaL5dMRPfnhetCZasVWOFwjFzPA@mail.gmail.com>
References: <CAFULd4bE_YZ22s_yeGia-REBmNnhA0dM+LvboFAh0XofkxpT4g@mail.gmail.com>	<CAK1BsWoqLikf6FdkteTRFP_ESpR-vkYDX3rLgQnZELChaAKxBw@mail.gmail.com>	<CAFULd4Zatns1RwNRv6-knWA0MEdCfnZbYd6Qaek81kSqiMXC+Q@mail.gmail.com>	<CAK1BsWpUdUg+ivi7pFdbUr8R45YjhbBCNhmN=98sMmW99dy-tg@mail.gmail.com>	<CAK1BsWo-iWDNcukpNqKsp7OrpE+k9riZV0=9Z3FxuGK+4DW24w@mail.gmail.com>	<CAFULd4Y3L0b8d+LPWgKuRtAx=W59gS6BANhE21e3PmEM8ZOWSQ@mail.gmail.com>	<CAK1BsWqZzaHoR-O_RFNT-HYJVXhgyotKfiK17FXV5Q83tg2_HQ@mail.gmail.com>	<CAFULd4at=44YLxXRyWvyxQzAFDdA32-vK-8WgDCAZuWR0cm5FQ@mail.gmail.com>	<CAK1BsWoJvbcu_icjUoXKs4dkaL5dMRPfnhetCZasVWOFwjFzPA@mail.gmail.com>
Date: Thu, 10 Jan 2013 11:28:00 -0000
Message-ID: <CAFULd4aHb13hDhP7ABqBsSbFX86Xqz_Vu56nJbZU5S5_TdEhNQ@mail.gmail.com>
Subject: Re: [RFC, x86] Changes for AVX and AVX2 processors
From: Uros Bizjak <ubizjak@gmail.com>
To: Vladimir Yakovlev <vbyakovl23@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Content-Type: text/plain; charset=ISO-8859-1
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
X-SW-Source: 2013-01/txt/msg00530.txt.bz2

On Thu, Jan 10, 2013 at 12:12 PM, Vladimir Yakovlev
<vbyakovl23@gmail.com> wrote:

> It seems I didn't sent a patch with last changes. Sorry if so.
>
> Vladimir
>
>  2012-12-27  Vladimir Yakovlev  <vladimir.b.yakovlev@intel.com
>
>          * config/i386/i386-c.c (ix86_target_macros_internal): New case.
>           (ix86_target_macros_internal): Likewise.
>
>          * config/i386/i386.c (m_CORE2I7): Removed.
>          (m_CORE_HASWELL): New macro.
>          (m_CORE_ALL): Likewise.
>          (initial_ix86_tune_features): m_CORE2I7 is replaced by m_CORE_ALL.
>          (initial_ix86_arch_features): Likewise.
>          (processor_target_table): Initializations for Core avx2.
>          (cpu_names): New names "core-avx2".
>          (ix86_option_override_internal): Changed PROCESSOR_COREI7 by
>          PROCESSOR_CORE_HASWELL.
>          (ix86_issue_rate): New case.
>          (ia32_multipass_dfa_lookahead): Likewise.
>          (ix86_sched_init_global): Likewise.
>
>          * config/i386/i386.h (TARGET_HASWELL): New macro.
>          (target_cpu_default): New TARGET_CPU_DEFAULT_haswell.
>          (processor_type): New PROCESSOR_HASWELL.

As strictly tuning patch, the patch is OK for mainline.

Please note, that (eventual) processor dispatcher patch will have to
wait for next stage1.

Thanks,
Uros.