public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113126] [14 Regression] ICE: in gimple_expand_vec_cond_expr, at gimple-isel.cc:325 at -O1
Date: Sun, 24 Dec 2023 08:39:47 +0000 [thread overview]
Message-ID: <bug-113126-4-gxQ6WLbRg8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113126-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113126
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2023-12-24
Ever confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
13:
h_6 = (G) f.0_1;
_2 = h_6 <= h_6;
_3 = VEC_COND_EXPR <_2, { -1, -1 }, { 0, 0 }>;
_4 = VIEW_CONVERT_EXPR<G>(_3);
14:
_2 = f.0_1 <= f.0_1;
_3 = VEC_COND_EXPR <_2, { -1, -1 }, { 0, 0 }>;
_4 = VIEW_CONVERT_EXPR<G>(_3);
Funny it was introduced accident by r14-2040-g6b32400e19a702 which is there to
fix a TYPE_PRECISION issue.
The result of `vector(2) float` is `vector(2) <signed-boolean:32>` but match
messes up here ...
Which means the patterns here are only valid for scalar conversions and not
vector based conversions or they need to add an conversion between the
resulting `vector boolean` types ...
next prev parent reply other threads:[~2023-12-24 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-24 8:27 [Bug tree-optimization/113126] New: " zsojka at seznam dot cz
2023-12-24 8:29 ` [Bug tree-optimization/113126] " pinskia at gcc dot gnu.org
2023-12-24 8:39 ` pinskia at gcc dot gnu.org [this message]
2024-01-08 14:00 ` rguenth at gcc dot gnu.org
2024-01-11 11:07 ` rguenth at gcc dot gnu.org
2024-01-11 14:13 ` cvs-commit at gcc dot gnu.org
2024-01-11 14:14 ` rguenth at gcc dot gnu.org
2024-01-12 7:21 ` liuhongt at gcc dot gnu.org
2024-01-12 8:54 ` 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-113126-4-gxQ6WLbRg8@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).