public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexander Monakov <amonakov@ispras.ru>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: "Joshi, Tejas Sanjay" <TejasSanjay.Joshi@amd.com>,
	 "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	 "Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>
Subject: Re: [PATCH][X86_64] Separate znver4 insn reservations from older znvers
Date: Tue, 3 Jan 2023 17:52:12 +0300 (MSK)	[thread overview]
Message-ID: <b601342a-2927-cb40-27d0-30d149a8c9f1@ispras.ru> (raw)
In-Reply-To: <Y7Q9XqD3fILtLSYC@kam.mff.cuni.cz>


On Tue, 3 Jan 2023, Jan Hubicka wrote:

> > 	* gcc/common/config/i386/i386-common.cc (processor_alias_table):
> > 	Use CPU_ZNVER4 for znver4.
> > 	* config/i386/i386.md: Add znver4.md.
> > 	* config/i386/znver4.md: New.
> OK,
> thanks!

Honza, I'm curious what are your further plans for this, you mentioned
merging znver4.md back in znver.md if I recall correctly?

Alexander

  reply	other threads:[~2023-01-03 14:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 16:18 Joshi, Tejas Sanjay
2022-11-14 18:51 ` Alexander Monakov
2022-11-15 12:08   ` Joshi, Tejas Sanjay
2022-11-15 12:51     ` Alexander Monakov
2022-11-21 11:40       ` Joshi, Tejas Sanjay
2022-11-21 15:30         ` Alexander Monakov
2022-12-01 11:28           ` Joshi, Tejas Sanjay
2022-12-01 19:01             ` Alexander Monakov
2022-12-12 21:41             ` Jan Hubička
2022-12-22 17:34               ` Joshi, Tejas Sanjay
2023-01-03 14:36                 ` Jan Hubicka
2023-01-03 14:52                   ` Alexander Monakov [this message]
2023-01-03 18:28                     ` Jan Hubicka
2023-01-05  5:52                   ` 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=b601342a-2927-cb40-27d0-30d149a8c9f1@ispras.ru \
    --to=amonakov@ispras.ru \
    --cc=TejasSanjay.Joshi@amd.com \
    --cc=Venkataramanan.Kumar@amd.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    /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).