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/113010] [RISCV] sign-extension lost in comparison with constant embedded in comma-op expression
Date: Thu, 04 Jan 2024 01:55:07 +0000 [thread overview]
Message-ID: <bug-113010-4-VfsRL5XsFG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113010-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113010
--- Comment #2 from Patrick O'Neill <patrick at rivosinc dot com> ---
Andrew I don't think this is a duplicate of pr112758 (or at least it wasn't
resolved by the fix for pr112758).
I still see the behavior on r14-6902-g4a0a8dc1b88.
> /scratch/tc-testing/tc-jan-3-trunk/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc -O2 -march=rv64gc red.c -o user-config.out
> QEMU_CPU=rv64,zbs=true timeout --verbose -k 0.1 1 /scratch/tc-testing/tc-jan-3-trunk/build-rv64gcv/bin/qemu-riscv64 user-config.out
> echo $? 1
next prev parent reply other threads:[~2024-01-04 1:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 21:55 [Bug target/113010] New: " gkm at rivosinc dot com
2023-12-13 22:06 ` [Bug target/113010] " pinskia at gcc dot gnu.org
2024-01-04 1:55 ` patrick at rivosinc dot com [this message]
2024-01-09 21:56 ` gkm at rivosinc dot com
2024-01-09 22:05 ` pinskia at gcc dot gnu.org
2024-01-09 22:12 ` pinskia at gcc dot gnu.org
2024-01-09 22:12 ` pinskia at gcc dot gnu.org
2024-01-11 2:45 ` gkm at rivosinc dot com
2024-01-11 2:50 ` gkm at rivosinc dot com
2024-01-24 21:33 ` patrick at rivosinc dot com
2024-01-24 21:47 ` pinskia at gcc dot gnu.org
2024-03-03 21:50 ` cvs-commit at gcc dot gnu.org
2024-03-03 21:53 ` law at gcc dot gnu.org
2024-03-04 18:24 ` cvs-commit 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-113010-4-VfsRL5XsFG@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).