From: Alexander Monakov <amonakov@ispras.ru>
To: "Joshi, Tejas Sanjay" <TejasSanjay.Joshi@amd.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"honza.hubicka@gmail.com" <honza.hubicka@gmail.com>,
"Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>
Subject: RE: [PATCH][X86_64] Separate znver4 insn reservations from older znvers
Date: Thu, 1 Dec 2022 22:01:56 +0300 (MSK) [thread overview]
Message-ID: <13c76b16-a479-efef-83f9-643a15a3629@ispras.ru> (raw)
In-Reply-To: <DM6PR12MB479566CF7A10C57A983BFC34E3149@DM6PR12MB4795.namprd12.prod.outlook.com>
On Thu, 1 Dec 2022, Joshi, Tejas Sanjay wrote:
> I have addressed all your comments in this revised patch, PFA and inlined below.
Thank you. Honza, please let me know if any further input is needed
from my side. For reference, here's how insn-automata.o table sizes
look with this patch (top 17, in bytes):
20068 r bdver1_fp_check
20068 r bdver1_fp_transitions
26208 r slm_min_issue_delay
27244 r bdver1_fp_min_issue_delay
28518 r glm_check
28518 r glm_transitions
33345 r znver4_fpu_min_issue_delay
33690 r geode_min_issue_delay
46980 r bdver3_fp_min_issue_delay
49428 r glm_min_issue_delay
53730 r btver2_fp_min_issue_delay
53760 r znver1_fp_transitions
93960 r bdver3_fp_transitions
106102 r lujiazui_core_check
106102 r lujiazui_core_transitions
133380 r znver4_fpu_transitions
196123 r lujiazui_core_min_issue_delay
There is a plan to further reduce Lujiazui and b[td]verX table sizes
by properly modeling division units like we did for znver.md (PR 87832).
Alexander
next prev parent reply other threads:[~2022-12-01 19:01 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 [this message]
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
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=13c76b16-a479-efef-83f9-643a15a3629@ispras.ru \
--to=amonakov@ispras.ru \
--cc=TejasSanjay.Joshi@amd.com \
--cc=Venkataramanan.Kumar@amd.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=honza.hubicka@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).