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] [RISCV] sign-extension lost in comparison with constant embedded in comma-op expression Date: Tue, 09 Jan 2024 21:56:32 +0000 [thread overview] Message-ID: <bug-113010-4-JfSPo5GN2B@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 Greg McGary <gkm at rivosinc dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #3 from Greg McGary <gkm at rivosinc dot com> --- This fixes it, though I would like second look from someone more familiar with the combiner: diff --git a/gcc/combine.cc b/gcc/combine.cc index 812553c091e..cd159db2a33 100644 --- a/gcc/combine.cc +++ b/gcc/combine.cc @@ -7208,6 +7208,10 @@ expand_compound_operation (rtx x) if (len == 0) return x; + /* Sign-extending loads can never be simplified at compile time. */ + if (MEM_P (XEXP (x, 0)) && load_extend_op (inner_mode) == SIGN_EXTEND) + return x; + break; case ZERO_EXTRACT:
next prev parent reply other threads:[~2024-01-09 21:56 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 2024-01-09 21:56 ` gkm at rivosinc dot com [this message] 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-JfSPo5GN2B@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).