public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Vladimir Yakovlev <vbyakovl23@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [RFC, x86] Changes for AVX and AVX2 processors
Date: Sun, 30 Dec 2012 18:05:00 -0000	[thread overview]
Message-ID: <CAFULd4at=44YLxXRyWvyxQzAFDdA32-vK-8WgDCAZuWR0cm5FQ@mail.gmail.com> (raw)
In-Reply-To: <CAK1BsWqZzaHoR-O_RFNT-HYJVXhgyotKfiK17FXV5Q83tg2_HQ@mail.gmail.com>

On Sun, Dec 30, 2012 at 5:05 PM, Vladimir Yakovlev <vbyakovl23@gmail.com> wrote:
> I fixed typos and added CalangeLog.
>
> 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.
>         (get_builtin_code_for_version): Likewise.
>
>         * config/i386/i386.h (TARGET_HASWELL): New macro.
>         (target_cpu_default): New TARGET_CPU_DEFAULT_haswell.
>         (processor_type): New PROCESSOR_HASWELL.

Please remove this part, it should be part of processor dispatcher part:

@@ -28705,6 +28712,10 @@ get_builtin_code_for_version (tree decl, tree
*predicate_list)
 	      arg_str = "corei7";
 	      priority = P_PROC_SSE4_2;
 	      break;
+	    case PROCESSOR_HASWELL:
+	      arg_str = "core-avx2";
+	      priority = P_PROC_SSE4_2;
+	      break;
 	    case PROCESSOR_ATOM:
 	      arg_str = "atom";
 	      priority = P_PROC_SSSE3;

Uros.

  reply	other threads:[~2012-12-30 18:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28 13:36 Uros Bizjak
2012-12-29  5:26 ` Vladimir Yakovlev
2012-12-29 10:07   ` Uros Bizjak
     [not found]     ` <CAK1BsWpUdUg+ivi7pFdbUr8R45YjhbBCNhmN=98sMmW99dy-tg@mail.gmail.com>
2012-12-29 16:57       ` Vladimir Yakovlev
2012-12-30 13:21         ` Uros Bizjak
2012-12-30 16:05           ` Vladimir Yakovlev
2012-12-30 18:05             ` Uros Bizjak [this message]
2013-01-10 11:12               ` Vladimir Yakovlev
2013-01-10 11:28                 ` Uros Bizjak
2013-01-10 11:31                   ` Jakub Jelinek
2013-01-11 11:25                     ` Vladimir Yakovlev
2013-01-11 11:27                       ` Jakub Jelinek
2013-01-11 12:15                         ` Vladimir Yakovlev
2013-01-11 12:21                           ` Uros Bizjak
2013-01-11 12:38                             ` Vladimir Yakovlev
2013-01-15 10:08                               ` Kirill Yukhin
2012-12-30 11:59       ` Uros Bizjak
  -- strict thread matches above, loose matches on Subject: below --
2012-12-27 17:07 Vladimir Yakovlev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFULd4at=44YLxXRyWvyxQzAFDdA32-vK-8WgDCAZuWR0cm5FQ@mail.gmail.com' \
    --to=ubizjak@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vbyakovl23@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).