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] [14] RISC-V rv64gcv: miscompile at -O3
Date: Mon, 15 Apr 2024 17:36:27 +0000	[thread overview]
Message-ID: <bug-114665-4-vphvQAeB7s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114665-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Patrick O'Neill <patrick at rivosinc dot com> ---
Reran as requested in pr114668. Still present with that fix.

I'll triage some other testcases and file those as well. Hopefully one of them
is a duplicate to this one that is easily reproducible.

GCC: r14-9976-gf8409c3109d
QEMU: v8.2.1 (f48c205fb42be48e2e47b7e1cd9a2802e5ca17b0)

Commands:
> /scratch/tc-testing/tc-apr-15/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc -march=rv64gcv -O3 red.c -o red.out
> /scratch/tc-testing/tc-apr-15/build-rv64gcv/bin/qemu-riscv64 red.out
35
> /scratch/tc-testing/tc-apr-15/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc red.c -o red.out
> /scratch/tc-testing/tc-apr-15/build-rv64gcv/bin/qemu-riscv64 red.out
FFFFFFB5

  parent reply	other threads:[~2024-04-15 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 19:56 [Bug target/114665] New: " patrick at rivosinc dot com
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 [this message]
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-vphvQAeB7s@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).