public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90275] [8/9/10 Regression] ICE: in insert_regs, at cse.c:1128 with -O2 -fno-dce -fno-tree-dce
Date: Mon, 06 Apr 2020 20:57:18 +0000	[thread overview]
Message-ID: <bug-90275-4-uXe2TEGXAk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90275-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90275

--- Comment #20 from Jeffrey A. Law <law at redhat dot com> ---
90275, the gift that keeps giving.   While the failure is similar, this feels
slightly different.

In this case we've got:

(insn 60 54 61 4 (parallel [
            (set (reg:CC 100 cc)
                (compare:CC (reg:SI 252 [ _5 ])
                    (const_int 0 [0])))
            (set (reg:SI 256 [ _5 ])
                (reg:SI 252 [ _5 ]))
        ]) "j.c":8:15 248 {*movsi_compare0}
     (expr_list:REG_UNUSED (reg:SI 256 [ _5 ])
        (nil)))


That gets (reg 252) into the tables.  We invalidate it when we hit this insn in
the same block:

(insn 65 64 66 4 (parallel [
            (set (reg:SI 252 [ _5 ])
                (mult:SI (reg:SI 252 [ _5 ])
                    (reg:SI 252 [ _5 ])))
            (set (reg:SI 253 [ _5+4 ])
                (truncate:SI (lshiftrt:DI (mult:DI (zero_extend:DI (reg:SI 252
[ _5 ]))
                            (zero_extend:DI (reg:SI 252 [ _5 ])))
                        (const_int 32 [0x20]))))
        ]) "j.c":8:9 68 {umull}
     (nil))

We then trigger the assert when handling this insn from the block:

(insn 174 173 175 4 (set (reg:SI 0 r0)
        (reg:SI 252 [ _5 ])) "j.c":8:20 241 {*arm_movsi_insn}
     (nil))

At the point where we simplify insn 60 into the form above, we don't know the
destination of the second set is unused.  That's not exposed until cse2 and I'm
not terribly inclined to do the DF analysis earlier and try to split that insn.

I'm not sure of the best fix here, nor is it clear why we're having so much
trouble with this code.  The real guts of this code hasn't changed materially
in decades.

  parent reply	other threads:[~2020-04-06 20:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-90275-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 22:14 ` [Bug rtl-optimization/90275] [8/9 " law at redhat dot com
2020-03-13  9:11 ` marxin at gcc dot gnu.org
2020-03-18 22:08 ` cvs-commit at gcc dot gnu.org
2020-03-23 23:59 ` cvs-commit at gcc dot gnu.org
2020-03-25 20:13 ` cvs-commit at gcc dot gnu.org
2020-03-25 20:33 ` cvs-commit at gcc dot gnu.org
2020-04-02 20:43 ` dcb314 at hotmail dot com
2020-04-03  7:18 ` [Bug rtl-optimization/90275] [8/9/10 " marxin at gcc dot gnu.org
2020-04-06 20:57 ` law at redhat dot com [this message]
2020-04-06 22:52 ` law at redhat dot com
2020-04-17 21:41 ` cvs-commit at gcc dot gnu.org
2021-05-04 12:32 ` [Bug rtl-optimization/90275] [8/9 " rguenth at gcc dot gnu.org
2021-05-14  9:51 ` [Bug rtl-optimization/90275] [9 " jakub at gcc dot gnu.org
2021-06-01  8:14 ` rguenth at gcc dot gnu.org
2021-09-28 14:50 ` dcb314 at hotmail dot com
2022-05-27  8:32 ` 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-90275-4-uXe2TEGXAk@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).