public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gkm at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113010] New: [RISCV] sign-extension lost in comparison with constant embedded in comma-op expression Date: Wed, 13 Dec 2023 21:55:45 +0000 [thread overview] Message-ID: <bug-113010-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113010 Bug ID: 113010 Summary: [RISCV] sign-extension lost in comparison with constant embedded in comma-op expression Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gkm at rivosinc dot com Target Milestone: --- Implicit conversion rules in C for comparing (unsigned long) with (int) require that (int) first widen to (long) extending sign, then convert to (unsigned long). I debugged this far enough to see that expand_compound_operation () in combine.cc converts (SIGN_EXTEND:DI (mem/c:SI ... )) into paradoxical (SUBREG:DI (mem/c:SI ... )), and thus loses the sign extension. It only happens when the constant comparand is within a comma operator. Test case: -------------------------------------------------- int minus_1 = -1; int main () { return ((0, 0xfffffffful) < minus_1) ? 0 : 1; } -------------------------------------------------- Godbolt: https://godbolt.org/z/xPMPzG1n1 The -march=rv64gc case begins to fail with gcc-13 The -march=rv64gc_zbs case begins to fail with gcc-12
next reply other threads:[~2023-12-13 21:55 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-13 21:55 gkm at rivosinc dot com [this message] 2023-12-13 22:06 ` [Bug target/113010] " pinskia at gcc dot gnu.org 2024-01-04 1:55 ` patrick at rivosinc dot com 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@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).