public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org, mjambor@suse.cz,
	Alexander Monakov <amonakov@ispras.ru>,
	"Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>,
	Tejas Sanjay <TejasSanjay.Joshi@amd.com>
Subject: Re: Zen4 tuning part 1 - cost tables
Date: Tue, 6 Dec 2022 12:24:55 +0100	[thread overview]
Message-ID: <Y48mh6lYmlp1uoBc@kam.mff.cuni.cz> (raw)
In-Reply-To: <CAFiYyc0SZ6aRW-UPhdq16FxU94NxRkkD+WvfN1+raw=N3yqpow@mail.gmail.com>

> > -  COSTS_N_INSNS (5),                   /* cost of FADD and FSUB insns.  */
> > -  COSTS_N_INSNS (5),                   /* cost of FMUL instruction.  */
> > +  COSTS_N_INSNS (7),                   /* cost of FADD and FSUB insns.  */
> > +  COSTS_N_INSNS (7),                   /* cost of FMUL instruction.  */
> >    /* Latency of fdiv is 8-15.  */
> >    COSTS_N_INSNS (15),                  /* cost of FDIV instruction.  */
> >    COSTS_N_INSNS (1),                   /* cost of FABS instruction.  */
> >    COSTS_N_INSNS (1),                   /* cost of FCHS instruction.  */
> >    /* Latency of fsqrt is 4-10.  */
> 
> the above comment looks like it needs updating as well

You are right. I will go through the comments for all zen revisions
incrementally.  Many of them are outdated are still referes to znver1.

Honza

  reply	other threads:[~2022-12-06 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 10:00 Jan Hubicka
2022-12-06 10:20 ` Richard Biener
2022-12-06 11:24   ` Jan Hubicka [this message]
2022-12-08  9:43 ` Kumar, Venkataramanan

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=Y48mh6lYmlp1uoBc@kam.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=TejasSanjay.Joshi@amd.com \
    --cc=Venkataramanan.Kumar@amd.com \
    --cc=amonakov@ispras.ru \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    --cc=richard.guenther@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).