public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hongtao Liu <crazylht@gmail.com>
To: Haochen Jiang <haochen.jiang@intel.com>
Cc: gcc-patches@gcc.gnu.org, hongtao.liu@intel.com
Subject: Re: [PATCH 1/2] Initial Raptorlake Support
Date: Mon, 17 Oct 2022 09:13:23 +0800	[thread overview]
Message-ID: <CAMZc-bxMu3vS4WCmTh5uzogfWuM3my6L_h3OP+9nMyanFvGerQ@mail.gmail.com> (raw)
In-Reply-To: <20221014074058.7709-2-haochen.jiang@intel.com>

On Fri, Oct 14, 2022 at 3:41 PM Haochen Jiang via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> gcc/ChangeLog:
>
>         * common/config/i386/cpuinfo.h:
>         (get_intel_cpu): Handle Raptorlake.
>         * common/config/i386/i386-common.cc:
>         (processor_alias_table): Add Raptorlake.
Ok.
> ---
>  gcc/common/config/i386/cpuinfo.h      | 2 ++
>  gcc/common/config/i386/i386-common.cc | 2 ++
>  2 files changed, 4 insertions(+)
>
> diff --git a/gcc/common/config/i386/cpuinfo.h b/gcc/common/config/i386/cpuinfo.h
> index bbced8a23b9..e759e6f89fa 100644
> --- a/gcc/common/config/i386/cpuinfo.h
> +++ b/gcc/common/config/i386/cpuinfo.h
> @@ -496,6 +496,8 @@ get_intel_cpu (struct __processor_model *cpu_model,
>      case 0x9a:
>      case 0xbf:
>        /* Alder Lake.  */
> +    case 0xb7:
> +      /* Raptor Lake.  */
>        cpu = "alderlake";
>        CHECK___builtin_cpu_is ("corei7");
>        CHECK___builtin_cpu_is ("alderlake");
> diff --git a/gcc/common/config/i386/i386-common.cc b/gcc/common/config/i386/i386-common.cc
> index c0c2ad74d87..8d346245ddd 100644
> --- a/gcc/common/config/i386/i386-common.cc
> +++ b/gcc/common/config/i386/i386-common.cc
> @@ -1929,6 +1929,8 @@ const pta processor_alias_table[] =
>      M_CPU_SUBTYPE (INTEL_COREI7_SAPPHIRERAPIDS), P_PROC_AVX512F},
>    {"alderlake", PROCESSOR_ALDERLAKE, CPU_HASWELL, PTA_ALDERLAKE,
>      M_CPU_SUBTYPE (INTEL_COREI7_ALDERLAKE), P_PROC_AVX2},
> +  {"raptorlake", PROCESSOR_ALDERLAKE, CPU_HASWELL, PTA_ALDERLAKE,
> +    M_CPU_SUBTYPE (INTEL_COREI7_ALDERLAKE), P_PROC_AVX2},
>    {"bonnell", PROCESSOR_BONNELL, CPU_ATOM, PTA_BONNELL,
>      M_CPU_TYPE (INTEL_BONNELL), P_PROC_SSSE3},
>    {"atom", PROCESSOR_BONNELL, CPU_ATOM, PTA_BONNELL,
> --
> 2.18.1
>


-- 
BR,
Hongtao

  reply	other threads:[~2022-10-17  1:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  7:40 [PATCH 0/2] Add new Intel Architecture Haochen Jiang
2022-10-14  7:40 ` [PATCH 1/2] Initial Raptorlake Support Haochen Jiang
2022-10-17  1:13   ` Hongtao Liu [this message]
2022-10-14  7:40 ` [PATCH 2/2] Initial Meteorlake Support Haochen Jiang
2022-10-17  1:13   ` Hongtao Liu

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=CAMZc-bxMu3vS4WCmTh5uzogfWuM3my6L_h3OP+9nMyanFvGerQ@mail.gmail.com \
    --to=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=haochen.jiang@intel.com \
    --cc=hongtao.liu@intel.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).