From: Alexander Monakov <amonakov@ispras.ru>
To: gcc-patches@gcc.gnu.org
Cc: "Jan Hubička" <honza.hubicka@gmail.com>,
"Joshi, Tejas Sanjay" <TejasSanjay.Joshi@amd.com>,
"Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>,
"Jan Hubicka" <hubicka@ucw.cz>, "Uros Bizjak" <ubizjak@gmail.com>
Subject: Re: [PATCH 0/2] i386: slim down insn-automata [PR 87832]
Date: Mon, 14 Nov 2022 14:19:29 +0300 (MSK) [thread overview]
Message-ID: <5ae6fc21-edc6-133-aee2-a41e16eb5b7@ispras.ru> (raw)
In-Reply-To: <866595d4-b6-e82b-b636-7743825046af@ispras.ru>
On Mon, 7 Nov 2022, Alexander Monakov wrote:
>
> On Tue, 1 Nov 2022, Alexander Monakov wrote:
>
> > Hi,
> >
> > I'm sending followup fixes for combinatorial explosion of znver scheduling
> > automaton tables as described in the earlier thread:
> >
> > https://inbox.sourceware.org/gcc-patches/23c795d6-403c-5927-e610-f0f1215f57ed@ispras.ru/T/#m36e069d43d07d768d4842a779e26b4a0915cc543
>
> AMD folks, do you have any feedback?
>
> What is the way forward for this patchset?
Ping?
> Alexander
>
> >
> > I think lujiazui.md and b[dt]ver[123].md have similar issues.
> >
> > Alexander Monakov (2):
> > i386: correct x87&SSE division modeling in znver.md
> > i386: correct x87&SSE multiplication modeling in znver.md
> >
> > gcc/config/i386/znver.md | 67 ++++++++++++++++++++--------------------
> > 1 file changed, 34 insertions(+), 33 deletions(-)
> >
> >
>
prev parent reply other threads:[~2022-11-14 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 16:26 Alexander Monakov
2022-11-01 16:26 ` [PATCH 1/2] i386: correct x87&SSE division modeling in znver.md Alexander Monakov
2022-11-01 16:26 ` [PATCH 2/2] i386: correct x87&SSE multiplication " Alexander Monakov
2022-11-16 11:53 ` Kumar, Venkataramanan
2022-11-16 12:21 ` Jan Hubička
2022-11-16 13:13 ` Alexander Monakov
2022-11-16 13:28 ` Jan Hubička
2022-11-07 11:27 ` [PATCH 0/2] i386: slim down insn-automata [PR 87832] Alexander Monakov
2022-11-14 11:19 ` Alexander Monakov [this message]
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=5ae6fc21-edc6-133-aee2-a41e16eb5b7@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 \
--cc=hubicka@ucw.cz \
--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).