public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112853] RISC-V: RVV: SPEC2017 525.x264 regression
Date: Tue, 05 Dec 2023 08:30:02 +0000	[thread overview]
Message-ID: <bug-112853-4-ibHjusJ1vn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112853-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112853

--- Comment #5 from Robin Dapp <rdapp at gcc dot gnu.org> ---
Can confirm.  The scalable build works with qemu vlen=128 but fails with
vlen=256.  That's a good data point as I'm not sure we're already covering this
with the current runs?

I'm going to start a testsuite run with -march=rv64gcv_zvl128b and qemu
vlen=256 to look for fallout.  Maybe this will already give us a clue before
extracting an x264 test case.

  parent reply	other threads:[~2023-12-05  8:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05  0:12 [Bug target/112853] New: " vineetg at gcc dot gnu.org
2023-12-05  0:14 ` [Bug target/112853] " vineetg at gcc dot gnu.org
2023-12-05  1:12 ` vineetg at gcc dot gnu.org
2023-12-05  6:51 ` juzhe.zhong at rivai dot ai
2023-12-05  7:43 ` juzhe.zhong at rivai dot ai
2023-12-05  8:30 ` rdapp at gcc dot gnu.org [this message]
2023-12-05 14:39 ` rdapp at gcc dot gnu.org
2023-12-05 14:42 ` rdapp at gcc dot gnu.org
2023-12-06 10:19 ` rdapp at gcc dot gnu.org
2023-12-11  9:47 ` cvs-commit at gcc dot gnu.org
2023-12-11  9:48 ` rdapp at gcc dot gnu.org

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=bug-112853-4-ibHjusJ1vn@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).