public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104511] [10/11/12 Regression] ICE: in emit_move_insn, at expr.cc:4010 with __builtin_convertvector() at -O
Date: Mon, 14 Feb 2022 08:53:33 +0000 [thread overview]
Message-ID: <bug-104511-4-uO0FQUokLu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104511-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104511
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-02-14
Target Milestone|--- |10.4
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
vector lowering produces
_5 = BIT_FIELD_REF <f_1(D), 64, 0>;
_6 = (_Decimal32) _5;
_7 = BIT_FIELD_REF <f_1(D), 64, 64>;
_8 = (_Decimal32) _7;
_9 = BIT_FIELD_REF <f_1(D), 64, 128>;
_10 = (_Decimal32) _9;
_11 = BIT_FIELD_REF <f_1(D), 64, 192>;
_12 = (_Decimal32) _11;
d_2 = {_6, _8, _10, _12};
where the BIT_FIELD_REFs extract _Float64. Then forwprop matches the
CTOR as VEC_PACK_TRUNC_EXPR from vector(2) _Float64 to vetor(4) _Decimal32.
_13 = BIT_FIELD_REF <f_1(D), 128, 0>;
_14 = BIT_FIELD_REF <f_1(D), 128, 128>;
d_2 = VEC_PACK_TRUNC_EXPR <_13, _14>;
I'm not sure if decimal FP vectors are a thing on powerpc64le and what their
ABI are. Maybe the testcase should be rejected.
Clearly the forwprop code is wrong here, since the vec_pack_trunc optab
has just a single mode there's no way to convert between DFP and FP.
I'll fix that, not sure if that will fix everything.
next prev parent reply other threads:[~2022-02-14 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 8:05 [Bug target/104511] New: " zsojka at seznam dot cz
2022-02-14 8:53 ` rguenth at gcc dot gnu.org [this message]
2022-02-14 10:26 ` [Bug target/104511] " cvs-commit at gcc dot gnu.org
2022-02-14 10:26 ` [Bug target/104511] [10/11 " rguenth at gcc dot gnu.org
2022-03-16 8:22 ` cvs-commit at gcc dot gnu.org
2022-03-16 9:22 ` [Bug target/104511] [10 " cvs-commit at gcc dot gnu.org
2022-03-16 9:24 ` 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-104511-4-uO0FQUokLu@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).