public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108547] ice in decompose, at wide-int.h:984 for -O2 with -Wall
Date: Wed, 25 Jan 2023 18:48:46 +0000	[thread overview]
Message-ID: <bug-108547-4-ZccA3UkEep@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108547-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I suspect it is trying to simplifying:
        ((NOT (us_8.1_2 != 0)))
        OR ((func_7_ptr_13.8_9 != 0) AND (_8 != 0) AND (func_7_ptr_13.8_9 & 1)
AND (NOT (_49 != 0)) AND (NOT (prephitmp_37 != 0)))
        OR ((func_7_ptr_13.8_9 & 1) AND (NOT (_49 != 0)) AND (NOT (_11 != 0)))
        OR ((NOT (_30 != 0)) AND (NOT (_49 != 0)) AND (NOT (prephitmp_37 !=
0)))

Note the & 1 there .... That seems like the issue, trying to simplify:
(func_7_ptr_13.8_9 != 0) AND (func_7_ptr_13.8_9 & 1)

  parent reply	other threads:[~2023-01-25 18:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 18:28 [Bug c/108547] New: " dcb314 at hotmail dot com
2023-01-25 18:40 ` [Bug tree-optimization/108547] " pinskia at gcc dot gnu.org
2023-01-25 18:43 ` pinskia at gcc dot gnu.org
2023-01-25 18:46 ` pinskia at gcc dot gnu.org
2023-01-25 18:48 ` pinskia at gcc dot gnu.org [this message]
2023-01-25 19:49 ` [Bug tree-optimization/108547] [13 Regression] " pinskia at gcc dot gnu.org
2023-01-26  7:45 ` rguenth at gcc dot gnu.org
2023-01-26  9:45 ` [Bug tree-optimization/108547] [13 Regression] ice in decompose, at wide-int.h:984 for -O2 with -Wall since r13-2500-g0a4a2667dc115ca7 marxin at gcc dot gnu.org
2023-01-26 12:49 ` cvs-commit at gcc dot gnu.org
2023-01-26 12:50 ` 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-108547-4-ZccA3UkEep@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).