public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <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 10:34:17 +0000 [thread overview]
Message-ID: <bug-104644-4-g7rmXdcqTd@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 #5 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 23 Feb 2022, jakub at gcc dot gnu.org wrote:
> 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.
Does it? I think it simply relies on the overflow being "sticky"
and not lost so that for bswap (100000000 * 1000000000) you get
sth with TREE_OVERFLOW. That's also what we do when folding
1(OVF) + 2, we return 3(OVF).
Sure, not folding is a possibility as well but isn't fold_const_call_1
eventually invoked from GIMPLE as well where TREE_OVERFLOW doens't
have any semantics?
I suppose we could use force_fit_type instead of wide_int_to_tree
for building the result here.
next prev parent reply other threads:[~2022-02-23 10:34 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
2022-02-23 10:34 ` rguenther at suse dot de [this message]
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-g7rmXdcqTd@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).