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/114668] New: [14] RISC-V rv64gcv: miscompile at -O3 Date: Tue, 09 Apr 2024 21:55:46 +0000 [thread overview] Message-ID: <bug-114668-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114668 Bug ID: 114668 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: char a; int b; short e[14]; char f[4][12544]; _Bool c[4][5]; int main() { for (int i = 0; i < 4; ++i) for (int l = 0; l < 15; ++l) for (int m = 0; m < 15; ++m) f[i][l * m] = 3; for (int j = 0; j < 4; j += 1) for (int k = 3; k < 13; k += 3) for (_Bool l = 0; l < 1; l = 1) for (int m = 0; m < 4; m += 1) { a = 0; b -= e[k]; c[j][m] = f[j][6]; } for (long i = 2; i < 4; ++i) __builtin_printf("%X\n", c[3][3]); } 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 1 FF > /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 1 1 Adjusting the f array to its minimal size of f[4][255] makes the issue go away. Looks similar to pr114665 so this might be a duplicate/related. Submitting this bug in case it's easier to understand the root cause. Found via fuzzer.
next reply other threads:[~2024-04-09 21:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-09 21:55 patrick at rivosinc dot com [this message] 2024-04-09 22:00 ` [Bug target/114668] " pinskia at gcc dot gnu.org 2024-04-10 15:35 ` rdapp at gcc dot gnu.org 2024-04-15 13:12 ` cvs-commit at gcc dot gnu.org 2024-04-15 13:17 ` 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-114668-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).