public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101443] internal compiler error: in wide_int_to_tree_1, at tree.c:1519
Date: Wed, 14 Jul 2021 10:18:37 +0000	[thread overview]
Message-ID: <bug-101443-4-TcQzAeSZVT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101443-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 51148
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51148&action=edit
gcc12-pr101443.patch

Untested fix.  I think it is best to optimize away these comparisons, as
NULLPTR_TYPE has only one possible value, we can always determine the result,
==, <= and >= will be always true and !=, < and > will be always false.
And keeping it around in the IL can break various optimizations, e.g. the range
stuff (in fold-const and reassoc), or dom, anything that will try to
build_int_cst 1 or -1 or something similar when it sees a comparison of
something with INTEGER_CST.

  parent reply	other threads:[~2021-07-14 10:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 19:43 [Bug c++/101443] New: " rawiener at amazon dot com
2021-07-13 20:04 ` [Bug c++/101443] " pinskia at gcc dot gnu.org
2021-07-13 20:29 ` rawiener at amazon dot com
2021-07-13 21:07 ` pinskia at gcc dot gnu.org
2021-07-14  9:13 ` jakub at gcc dot gnu.org
2021-07-14 10:18 ` jakub at gcc dot gnu.org [this message]
2021-07-14 10:22 ` [Bug c++/101443] [9/10/11/12 Regression] " jakub at gcc dot gnu.org
2021-07-15 16:54 ` cvs-commit at gcc dot gnu.org
2021-07-15 16:55 ` [Bug c++/101443] [9/10/11 " jakub at gcc dot gnu.org
2021-07-18 23:29 ` cvs-commit at gcc dot gnu.org
2021-07-19  7:55 ` [Bug c++/101443] [9/10 " jakub at gcc dot gnu.org
2022-05-10  8:19 ` cvs-commit at gcc dot gnu.org
2022-05-11  6:21 ` cvs-commit at gcc dot gnu.org
2022-05-11  6:36 ` jakub at gcc dot gnu.org
2024-02-27 16:16 ` rawiener at amazon dot com

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-101443-4-TcQzAeSZVT@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).