public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105663] [11/12/13 Regression] ICE (segfault) in operator_bitwise_not::fold_range with O2/O3
Date: Fri, 20 May 2022 06:37:19 +0000	[thread overview]
Message-ID: <bug-105663-4-YNkgJYtZi5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105663-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
bitwise and is allowed for pointers on GIMPLE for alignment purposes and to
avoid round-trips to/from integer types for this.  It's only natural to then
allow all bit operations on pointers (and hard to excempt some given we have
many patterns transforming between them).  It looks like also MIN/MAX is
allowed (why not, we also allow relational compares), but BIT_NOT is
explicitely disallowed.

I think we simply have to accept those operations on pointers or decide
allowing
BIT_AND was a mistake and remove support for all of them.

  parent reply	other threads:[~2022-05-20  6:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19 15:47 [Bug c/105663] New: Segmentation Fault on optimization level O2/O3 r.j.dejong at student dot utwente.nl
2022-05-19 15:52 ` [Bug tree-optimization/105663] [12/13 Regression] ICE (segfault) in operator_bitwise_not::fold_range with O2/O3 pinskia at gcc dot gnu.org
2022-05-19 16:14 ` pinskia at gcc dot gnu.org
2022-05-19 16:19 ` pinskia at gcc dot gnu.org
2022-05-19 16:35 ` amacleod at redhat dot com
2022-05-19 16:37 ` amacleod at redhat dot com
2022-05-19 20:23 ` marxin at gcc dot gnu.org
2022-05-19 20:26 ` [Bug tree-optimization/105663] [11/12/13 " pinskia at gcc dot gnu.org
2022-05-20  6:37 ` rguenth at gcc dot gnu.org [this message]
2022-05-20  6:37 ` rguenth at gcc dot gnu.org
2022-05-20  6:38 ` rguenth at gcc dot gnu.org
2022-05-20 10:44 ` [Bug tree-optimization/105663] [11/12/13 Regression] ICE (segfault) in operator_bitwise_not::fold_range with O1/O2/O3/Os gcc-hbfypl at hansdejong dot eu
2022-10-31 18:55 ` pinskia 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-105663-4-YNkgJYtZi5@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).