public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113206] New: [14] RISC-V rv64gcv vector: Runtime mismatch with rv64gc Date: Tue, 02 Jan 2024 19:08:33 +0000 [thread overview] Message-ID: <bug-113206-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113206 Bug ID: 113206 Summary: [14] RISC-V rv64gcv vector: Runtime mismatch with rv64gc Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: patrick at rivosinc dot com Target Milestone: --- Testcase: signed char e; short f = 8; signed d; int(g)(int o, int r) { return o & (o ^ -1) < 0 ? o : o - r; } #pragma pack(1) struct { short h; unsigned : 18; short i; long j; int k; char l; long m; int n; } a, b, s, c, *p = &b, *u = &s, q = {1}; void t() { *p = a; for (; e > -7; e = g(e, 8)) ; q = *u = c; for (; d - 3; d = 3) ; } int main() { t(); if (f == 8) return 0; else return 1; } Commands: rv64gcv: > /scratch/tc-testing/tc-jan-1-trunk/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc -march=rv64gcv -O3 red.c -o user-config.out > QEMU_CPU=rv64,vlen=128,v=true,vext_spec=v1.0,Zve32f=true,Zve64f=true timeout --verbose -k 0.1 1 /scratch/tc-testing/tc-dec-22-trunk/build-rv64gcv/bin/qemu-riscv64 user-config.out > echo $? 1 rv64gc: > /scratch/tc-testing/tc-jan-1-trunk/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc -march=rv64gc -O3 red.c -o user-config.out > QEMU_CPU=rv64,vlen=128,v=true,vext_spec=v1.0,Zve32f=true,Zve64f=true timeout --verbose -k 0.1 1 /scratch/tc-testing/tc-dec-22-trunk/build-rv64gcv/bin/qemu-riscv64 user-config.out > echo $? 0 Nothing touches f, so it should still be 8 after the function.
next reply other threads:[~2024-01-02 19:08 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-02 19:08 patrick at rivosinc dot com [this message] 2024-01-02 23:20 ` [Bug target/113206] " juzhe.zhong at rivai dot ai 2024-01-02 23:26 ` patrick at rivosinc dot com 2024-01-03 1:15 ` juzhe.zhong at rivai dot ai 2024-01-04 0:33 ` cvs-commit at gcc dot gnu.org 2024-01-04 0:47 ` juzhe.zhong at rivai dot ai 2024-01-04 1:36 ` patrick at rivosinc dot com 2024-01-04 2:32 ` patrick at rivosinc dot com 2024-01-04 3:46 ` juzhe.zhong at rivai dot ai 2024-01-04 16:44 ` patrick at rivosinc dot com
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-113206-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: linkBe 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).