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 02:04:52 +0000	[thread overview]
Message-ID: <bug-102133-4-EScCgy4VCU@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 #3 from Hongtao.liu <crazylht at gmail dot com> ---
static inline void
set_rtl (tree t, rtx x)
{
  gcc_checking_assert (!x
                       || !(TREE_CODE (t) == SSA_NAME || is_gimple_reg (t))
                       || (use_register_for_decl (t)
                           ? (REG_P (x)
                              || (GET_CODE (x) == CONCAT
                                  && (REG_P (XEXP (x, 0))
                                      || SUBREG_P (XEXP (x, 0)))
                                  && (REG_P (XEXP (x, 1))
                                      || SUBREG_P (XEXP (x, 1))))
                              /* We need to accept PARALLELs for RESUT_DECLs
                                 because of vector types with BLKmode returned
                                 in multiple registers, but they are supposed
                                 to be uncoalesced.  */
                              || (GET_CODE (x) == PARALLEL
                                  && SSAVAR (t)
                                  && TREE_CODE (SSAVAR (t)) == RESULT_DECL
                                  && (GET_MODE (x) == BLKmode
                                      || !flag_tree_coalesce_vars)))
                           : (MEM_P (x) || x == pc_rtx
                              || (GET_CODE (x) == CONCAT
                                  && MEM_P (XEXP (x, 0))
                                  && MEM_P (XEXP (x, 1))))));


x is 
(subreg:DF (reg:DI 154) 0),

t is 
 <ssa_name 0x7fffea4a9a68
    type <real_type 0x7fffea48b1f8 DFtype sizes-gimplified DF
        size <integer_cst 0x7fffea2e2e10 constant 64>
        unit-size <integer_cst 0x7fffea2e2e28 constant 8>
        align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7fffea2f9498 precision:64 context <translation_unit_decl 0x7fffea49c078
/scratch/jmyers/glibc/many12/src/gcc/libgcc/libgcc2.c>>
    visited var <parm_decl 0x7fffea497b00 d>
    def_stmt GIMPLE_NOP
    version:62>

and it hit REG_P (XEXP (x, 1)), XEXP (x, 1) is invalid for subreg, so set_rtl 
here doesn't accept subreg?

  parent reply	other threads:[~2021-08-31  2:04 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 [this message]
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
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-EScCgy4VCU@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).