public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vineetg@rivosinc.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
	Robin Dapp <rdapp.gcc@gmail.com>,
	Palmer Dabbelt <palmer@rivosinc.com>,
	Kito Cheng <kito.cheng@sifive.com>,
	"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
	jeremy.bennett@embecosm.com
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	gnu-toolchain <gnu-toolchain@rivosinc.com>
Subject: State of risc-v port in the current merge, revert, rinse-repeat commotion
Date: Wed, 24 Apr 2024 10:58:58 -0700	[thread overview]
Message-ID: <58137772-cd2b-489a-9687-db4a03b8578f@rivosinc.com> (raw)

Hi,

Per discussion in patchworks call yesterday I gave the trunk snapshot a
spin for SPEC2017 build/runs on QEMU (usual flags -Ofast -flto=auto,
-march=rv64gcv_zba_zbb_zbs_zicond)

     2024-04-23 6f0a646dd2fc Remove repeated information in
-ftree-loop-distribute-patterns doc  

The dynamic icounts looks sane (vs. Apr 10 snapshot) except for a
regression in x264 which is likely independent of the chaos going on.

     Apr 10     |     Apr 23      |
  109f1b28fc94  |  6f0a646dd2fc   |
----------------+-----------------+--------
276,584,692,883 | 277,816,987,018 |  -0.45%
913,452,236,000 | 927,291,935,180 |  -1.52%
903,916,092,805 | 915,364,006,176 |  -1.27%

cheers,
-Vineet

             reply	other threads:[~2024-04-24 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 17:58 Vineet Gupta [this message]
2024-04-24 19:22 ` Robin Dapp
2024-04-24 22:58   ` Vineet Gupta

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=58137772-cd2b-489a-9687-db4a03b8578f@rivosinc.com \
    --to=vineetg@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu-toolchain@rivosinc.com \
    --cc=jeffreyalaw@gmail.com \
    --cc=jeremy.bennett@embecosm.com \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@sifive.com \
    --cc=palmer@rivosinc.com \
    --cc=rdapp.gcc@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).