public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107368] [13 Regression] ICE: 'verify_gimple' failed (error: non-trivial conversion in 'var_decl')
Date: Tue, 25 Oct 2022 08:45:14 +0000 [thread overview]
Message-ID: <bug-107368-4-l7C0gC3XEF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107368-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107368
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:44e18da4d9c5faf189fe876986927be12ae4e4c4
commit r13-3481-g44e18da4d9c5faf189fe876986927be12ae4e4c4
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Oct 25 10:42:59 2022 +0200
gimplify: Call gimple_boolify on IFN_ASSUME argument [PR107368]
The following testcase ICEs in C, because assume attribute condition
has int type rather than bool and the gimplification into GIMPLE_ASSUME
assigns it into a bool variable.
Fixed by calling gimple_boolify.
2022-10-25 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/107368
* gimplify.cc (gimplify_call_expr): For complex IFN_ASSUME
conditions call gimple_boolify on the condition.
* gcc.dg/attr-assume-5.c: New test.
next prev parent reply other threads:[~2022-10-25 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 5:46 [Bug tree-optimization/107368] New: " asolokha at gmx dot com
2022-10-24 8:04 ` [Bug tree-optimization/107368] " marxin at gcc dot gnu.org
2022-10-24 9:19 ` jakub at gcc dot gnu.org
2022-10-24 13:16 ` rguenth at gcc dot gnu.org
2022-10-25 8:45 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-25 8:51 ` jakub 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-107368-4-l7C0gC3XEF@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).