From: "Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>
To: "Joshi, Tejas Sanjay" <TejasSanjay.Joshi@amd.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "honza.hubicka@gmail.com" <honza.hubicka@gmail.com>,
Uros Bizjak <ubizjak@gmail.com>
Subject: RE: [PATCH] [X86_64]: Enable support for next generation AMD Zen4 CPU
Date: Fri, 21 Oct 2022 09:59:26 +0000 [thread overview]
Message-ID: <DM6PR12MB30817FA964B5CC83AA25E3F28F2D9@DM6PR12MB3081.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DM6PR12MB47951AA15063BEF7ACF91688E3299@DM6PR12MB4795.namprd12.prod.outlook.com>
Hi all,
> -----Original Message-----
> From: Joshi, Tejas Sanjay <TejasSanjay.Joshi@amd.com>
> Sent: Monday, October 17, 2022 8:09 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Kumar, Venkataramanan <Venkataramanan.Kumar@amd.com>;
> honza.hubicka@gmail.com; Uros Bizjak <ubizjak@gmail.com>
> Subject: RE: [PATCH] [X86_64]: Enable support for next generation AMD
> Zen4 CPU
>
> [Public]
>
> Hi,
>
> > BTW: Perhaps znver1.md is not the right filename anymore, since it hosts
> all four Zen schedulers.
>
> I have renamed the file to znver.md in this revision, PFA.
> Thank you for the review, we will push it for trunk if we don't get any
> further comments.
I have pushed the patch on behalf of Tejas.
Regards,
Venkat.
next prev parent reply other threads:[~2022-10-21 9:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 15:32 Joshi, Tejas Sanjay
2022-10-16 17:48 ` Uros Bizjak
2022-10-17 14:39 ` Joshi, Tejas Sanjay
2022-10-21 9:59 ` Kumar, Venkataramanan [this message]
2022-10-21 11:51 ` Richard Biener
2022-10-21 12:52 ` Jan Hubicka
2022-10-21 14:02 ` Joshi, Tejas Sanjay
2022-10-21 17:59 ` Joshi, Tejas Sanjay
2022-10-22 17:11 ` Jakub Jelinek
2022-10-23 14:29 ` Kumar, Venkataramanan
2022-10-24 14:26 ` Alexander Monakov
2022-10-24 14:40 ` Jan Hubička
2022-10-24 18:47 ` Alexander Monakov
2022-10-26 18:07 ` Kumar, Venkataramanan
2022-10-26 18:23 ` Alexander Monakov
2022-10-31 10:39 ` Joshi, Tejas Sanjay
2022-10-31 10:59 ` Jan Hubička
2022-11-01 12:22 ` Alexander Monakov
2022-10-25 9:17 ` Joshi, Tejas Sanjay
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=DM6PR12MB30817FA964B5CC83AA25E3F28F2D9@DM6PR12MB3081.namprd12.prod.outlook.com \
--to=venkataramanan.kumar@amd.com \
--cc=TejasSanjay.Joshi@amd.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=honza.hubicka@gmail.com \
--cc=ubizjak@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).