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/114665] New: [14] RISC-V rv64gcv: miscompile at -O3 Date: Tue, 09 Apr 2024 19:56:23 +0000 [thread overview] Message-ID: <bug-114665-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114665 Bug ID: 114665 Summary: [14] RISC-V rv64gcv: miscompile at -O3 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 b; _Bool c[15][15]; int main() { for (long f = 0; f < 5; ++f) for (long g = 0; g < 5; ++g) c[f][g] = 1; _Bool(*h)[15] = c; for (int f = 0; f < 15; f += 1) for (int g = 0; g < 15; g += 1) b -= c[g][g] ? c[g][g] : h[f][g]; __builtin_printf("%X\n", b); } Commands: > /scratch/tc-testing/tc-apr-9/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc -march=rv64gcv -O3 red.c -o red.out > /scratch/tc-testing/tc-apr-9/build-rv64gcv/bin/qemu-riscv64 red.out 35 > /scratch/tc-testing/tc-apr-9/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc -march=rv64gcv -O2 red.c -o red.out > /scratch/tc-testing/tc-apr-9/build-rv64gcv/bin/qemu-riscv64 red.out FFFFFFB5 Discovered/tested using r14-9877-g1f719aa7c0d (not bisected) Found via fuzzer.
next reply other threads:[~2024-04-09 19:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-09 19:56 patrick at rivosinc dot com [this message] 2024-04-10 12:09 ` [Bug target/114665] " rdapp at gcc dot gnu.org 2024-04-10 12:42 ` rdapp at gcc dot gnu.org 2024-04-10 17:43 ` patrick at rivosinc dot com 2024-04-15 17:36 ` patrick at rivosinc dot com 2024-04-15 18:56 ` rdapp at gcc dot gnu.org 2024-04-15 20:34 ` 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-114665-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).