public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/102133] [12 Regression] ICE in set_rtl building libgcc __muldc3 for 32-bit SPARC Date: Tue, 31 Aug 2021 03:29:09 +0000 [thread overview] Message-ID: <bug-102133-4-tAGjrWzGtM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102133-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102133 --- Comment #7 from Hongtao.liu <crazylht at gmail dot com> --- Since we also allow something like (concat:(subreg) (subreg)), should we also allow subreg outside? gcc_checking_assert (!x || !(TREE_CODE (t) == SSA_NAME || is_gimple_reg (t)) || (use_register_for_decl (t) - ? (REG_P (x) + ? (REG_P (x) || SUBREG_P (x) || (GET_CODE (x) == CONCAT && (REG_P (XEXP (x, 0)) || SUBREG_P (XEXP (x, 0))) The below code also looks like it's going to handle SUBREG. if (x) { bool skip = false; tree cur = NULL_TREE; rtx xm = x; retry: if (MEM_P (xm)) cur = MEM_EXPR (xm); else if (REG_P (xm)) cur = REG_EXPR (xm); else if (SUBREG_P (xm)) { gcc_assert (subreg_lowpart_p (xm)); xm = SUBREG_REG (xm); goto retry;
next prev parent reply other threads:[~2021-08-31 3:29 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-30 19:03 [Bug middle-end/102133] New: " jsm28 at gcc dot gnu.org 2021-08-30 19:09 ` [Bug middle-end/102133] " pinskia at gcc dot gnu.org 2021-08-31 1:20 ` crazylht at gmail dot com 2021-08-31 1:51 ` crazylht at gmail dot com 2021-08-31 2:04 ` crazylht at gmail dot com 2021-08-31 2:16 ` crazylht at gmail dot com 2021-08-31 2:49 ` crazylht at gmail dot com 2021-08-31 3:01 ` crazylht at gmail dot com 2021-08-31 3:29 ` crazylht at gmail dot com [this message] 2021-08-31 4:59 ` crazylht at gmail dot com 2021-08-31 7:23 ` rguenth at gcc dot gnu.org 2021-08-31 10:09 ` mikpelinux at gmail dot com 2021-09-01 1:08 ` cvs-commit at gcc dot gnu.org 2021-09-01 1:24 ` crazylht at gmail dot com 2022-01-17 13:52 ` rguenth 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-102133-4-tAGjrWzGtM@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).