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 tree-optimization/104644] [12 Regression] ICE: SIGSEGV (infinite recursion in fold_binary_loc / fold_build2_loc / generic_simplify_NE_EXPR)
Date: Wed, 23 Feb 2022 08:27:17 +0000	[thread overview]
Message-ID: <bug-104644-4-z3YAC54ygH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104644-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think the FEs rely on such trees not being folded.
It is done in fold-const-call.cc,
1186    static tree
1187    fold_const_call_1 (combined_fn fn, tree type, tree arg)
1188    {
1189      machine_mode mode = TYPE_MODE (type);
1190      machine_mode arg_mode = TYPE_MODE (TREE_TYPE (arg));
1191    
1192      if (integer_cst_p (arg))
1193        {
and integer_cst_p does:
35      /* Functions that test for certain constant types, abstracting away the
36         decision about whether to check for overflow.  */
37      
38      static inline bool
39      integer_cst_p (tree t)
40      {
41        return TREE_CODE (t) == INTEGER_CST && !TREE_OVERFLOW (t);
42      }

  parent reply	other threads:[~2022-02-23  8:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 18:38 [Bug c/104644] New: " zsojka at seznam dot cz
2022-02-22 18:45 ` [Bug tree-optimization/104644] " jakub at gcc dot gnu.org
2022-02-22 19:07 ` jakub at gcc dot gnu.org
2022-02-23  8:14 ` rguenth at gcc dot gnu.org
2022-02-23  8:27 ` jakub at gcc dot gnu.org [this message]
2022-02-23 10:34 ` rguenther at suse dot de
2022-02-23 13:42 ` cvs-commit at gcc dot gnu.org
2022-02-23 13:43 ` 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-104644-4-z3YAC54ygH@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).