public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Joshi, Tejas Sanjay" <TejasSanjay.Joshi@amd.com>
Cc: "hjl.tools@gmail.com" <hjl.tools@gmail.com>,
	"Gopalasubramanian, Ganesh" <Ganesh.Gopalasubramanian@amd.com>,
	"Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>,
	"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH] Add AMD znver5 processor support
Date: Fri, 22 Dec 2023 12:15:45 +0100	[thread overview]
Message-ID: <10a2df3f-dd24-44d3-88db-8e52c28ae884@suse.com> (raw)
In-Reply-To: <DM6PR12MB479500B6E1D54C8C60A7B454E394A@DM6PR12MB4795.namprd12.prod.outlook.com>

On 22.12.2023 08:12, Joshi, Tejas Sanjay wrote:
> PFA the patch for AMD znver5 processor enablement. The patch adds the following changes:
> 
>         * New AMD znver5 processor support:
>            In addition to znver4 features, the architecture adds the following features:
>                 * AVX_VNNI, MOVDIRI, MOVDIR64B, AVX512_VP2INTERSECT, PREFETCHI
>         * New test files added:
>                 * arch-15.s: New ISAs supported under the arch.
>                 * x86-64-arch-5.s: x86-64 version of the test.
> 
> Make check passes on x86-64. Good to submit in trunk?

Looks okay, so yes.

Jan

  reply	other threads:[~2023-12-22 11:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22  7:12 Joshi, Tejas Sanjay
2023-12-22 11:15 ` Jan Beulich [this message]
2023-12-26  3:29   ` Joshi, Tejas Sanjay
2024-01-04  8:19     ` Jan Beulich
2024-01-04  9:30       ` Joshi, Tejas Sanjay
2024-01-05  8:29         ` Jan Beulich
2024-01-05  9:35           ` Nick Clifton
2024-01-05 11:11             ` Jan Beulich

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=10a2df3f-dd24-44d3-88db-8e52c28ae884@suse.com \
    --to=jbeulich@suse.com \
    --cc=Ganesh.Gopalasubramanian@amd.com \
    --cc=TejasSanjay.Joshi@amd.com \
    --cc=Venkataramanan.Kumar@amd.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@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).