public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vineetg at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112853] New: RISC-V: RVV: SPEC2017 525.x264 regression
Date: Tue, 05 Dec 2023 00:12:41 +0000 [thread overview]
Message-ID: <bug-112853-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112853
Bug ID: 112853
Summary: RISC-V: RVV: SPEC2017 525.x264 regression
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: vineetg at gcc dot gnu.org
CC: juzhe.zhong at rivai dot ai, patrick at rivosinc dot com,
rdapp at gcc dot gnu.org
Target Milestone: ---
As of commit 3d104d93a701 ("ARC: Consistent use of whitespace in assembler
templates.") x264 build for RVV is segfaulting.
```
QEMU_CPU=rv64,vlen=256,zba=true,zbb=true,zbs=true,zicond=true,vext_spec=v1.0,Zve32f=true,Zve64f=true
qemu-riscv64 ./ldecod_r_base.rivos_rv64-m64 -i BuckBunny.264 -o BuckBunny.yuv
Setting Default Parameters...
Parsing Configfile decoder.cfg
----------------------------- JM 17.1 (FRExt) -----------------------------
--------------------------------------------------------------------------
Input H.264 bitstream : BuckBunny.264
Output decoded YUV : BuckBunny.yuv
Input reference file : test_rec.yuv
--------------------------------------------------------------------------
POC must = frame# or field# for SNRs to be correct
--------------------------------------------------------------------------
Frame POC Pic# QP SnrY SnrU SnrV Y:U:V Time(ms)
--------------------------------------------------------------------------
Input reference file : test_rec.yuv does not exist
SNR values are not available
Segmentation fault (core dumped)
```
It was fine at my prev checkpoint:
2023-11-22 6f59f959e751 hppa: Define MAX_FIXED_MODE_SIZE
Built with following flags
-Ofast -fno-lto -static -march=rv64gcv_zba_zbb_zbc_zbs_zicond -ftree-vectorize
--param=riscv-autovec-preference=scalable
next reply other threads:[~2023-12-05 0:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 0:12 vineetg at gcc dot gnu.org [this message]
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
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@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).