public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acsawdey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96791] ICE in convert_mode_scalar, at expr.c:412
Date: Fri, 28 Aug 2020 00:58:52 +0000 [thread overview]
Message-ID: <bug-96791-4-dFmcI60j1t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96791-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96791
acsawdey at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |acsawdey at gcc dot gnu.org
--- Comment #5 from acsawdey at gcc dot gnu.org ---
Nope, this is my patch that added vector pair to memcpy/memmove expansion. We
apparently don't have the right patterns defined for this to extract things
from the POImode reg that it uses.
This is the code in expr.c:
if (GET_MODE_CLASS (from_mode) == MODE_PARTIAL_INT)
{
rtx new_from;
scalar_int_mode full_mode
= smallest_int_mode_for_size (GET_MODE_BITSIZE (from_mode));
convert_optab ctab = unsignedp ? zext_optab : sext_optab;
enum insn_code icode;
icode = convert_optab_handler (ctab, full_mode, from_mode);
gcc_assert (icode != CODE_FOR_nothing);
convert_optab_handler doesn't find anything to go from POImode to DImode, so
the assert fires.
next prev parent reply other threads:[~2020-08-28 0:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 3:33 [Bug target/96791] New: " asolokha at gmx dot com
2020-08-27 18:50 ` [Bug target/96791] " dje at gcc dot gnu.org
2020-08-27 19:24 ` wschmidt at gcc dot gnu.org
2020-08-27 19:38 ` acsawdey at gcc dot gnu.org
2020-08-27 23:21 ` wschmidt at gcc dot gnu.org
2020-08-28 0:58 ` acsawdey at gcc dot gnu.org [this message]
2020-08-31 9:28 ` asolokha at gmx dot com
2020-08-31 14:20 ` acsawdey at gcc dot gnu.org
2020-09-02 14:02 ` acsawdey at gcc dot gnu.org
2020-09-09 23:32 ` acsawdey at gcc dot gnu.org
2020-09-11 2:18 ` acsawdey at gcc dot gnu.org
2020-11-17 16:10 ` cvs-commit at gcc dot gnu.org
2020-11-24 2:46 ` asolokha at gmx dot com
2020-11-24 2:47 ` asolokha at gmx dot com
2020-11-25 0:49 ` bergner at gcc dot gnu.org
2020-11-25 1:04 ` segher at gcc dot gnu.org
2020-11-25 1:06 ` segher at gcc dot gnu.org
2020-11-25 3:29 ` asolokha at gmx dot com
2020-11-25 20:10 ` bergner at gcc dot gnu.org
2020-11-25 20:31 ` segher at gcc dot gnu.org
2020-11-25 20:39 ` segher at gcc dot gnu.org
2020-11-25 20:42 ` bergner at gcc dot gnu.org
2020-11-25 21:12 ` meissner at gcc dot gnu.org
2020-11-25 22:28 ` segher at gcc dot gnu.org
2021-09-02 22:15 ` bergner at gcc dot gnu.org
2021-09-02 22:53 ` segher 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-96791-4-dFmcI60j1t@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).