public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdapp at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/104153] [12 Regression] ICE due to recent ifcvt changes
Date: Fri, 21 Jan 2022 10:56:15 +0000	[thread overview]
Message-ID: <bug-104153-4-FlvtWrvGh7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104153-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from rdapp at linux dot ibm.com ---
I was able to reproduce the ICE on a cross compiler. Curiously, we do not even
succeed with if-conversion here but nevertheless emit an insn

(jump_insn 78 9 79 6 (set (pc)
        (if_then_else (ne:BI (reg:BI 34 ?sr_f)
                (reg:SI 160))
            (label_ref:SI 218)
            (pc)))
"../../../../../../..//newlib-cygwin/newlib/libm/math/s_floor.c":90:14 77
{*cbranch}
     (expr_list:REG_DEAD (reg:BI 34 ?sr_f)
        (int_list:REG_BR_PROB 536870916 (nil)))
 -> 218)

while reg:SI 160 is nowhere to be found.

Most likely the way I emit the sequences has side effects that I failed to
properly revert.  Everything should be inside

begin_sequence ()
end_sequence ()

blocks but that is not sufficient.  I guess if the optabs interfaces are
exposed and used like in the patch we also need delete_insns_since () or
similar?  The problem is most likely latent on other targets as well.

  parent reply	other threads:[~2022-01-21 10:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21  0:12 [Bug rtl-optimization/104153] New: " law at gcc dot gnu.org
2022-01-21  0:14 ` [Bug rtl-optimization/104153] " pinskia at gcc dot gnu.org
2022-01-21  8:50 ` rguenth at gcc dot gnu.org
2022-01-21 10:56 ` rdapp at linux dot ibm.com [this message]
2022-01-21 18:23 ` law at gcc dot gnu.org
2022-01-21 21:03 ` rdapp at linux dot ibm.com
2022-01-24  8:51 ` pinskia at gcc dot gnu.org
2022-01-28  7:40 ` law at gcc dot gnu.org
2022-01-31  7:24 ` rdapp at linux dot ibm.com
2022-01-31 17:50 ` rdapp at linux dot ibm.com
2022-01-31 18:19 ` law at gcc dot gnu.org
2022-02-08  8:47 ` shorne at gcc dot gnu.org
2022-02-08  8:48 ` shorne at gcc dot gnu.org
2022-02-08 19:49 ` cvs-commit at gcc dot gnu.org
2022-02-13 18:29 ` law 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-104153-4-FlvtWrvGh7@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).