public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101322] ICE in copy_to_mode_reg, at explow.c:651
Date: Fri, 26 Aug 2022 19:15:48 +0000 [thread overview]
Message-ID: <bug-101322-4-yeuWru12A0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101322-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101322
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-08-26
Target|powerpc-*-linux-gnu |powerpc*-*-linux-gnu
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |bergner at gcc dot gnu.org
--- Comment #1 from Peter Bergner <bergner at gcc dot gnu.org> ---
Confirmed. I see what the problem is. When we expand the built-in, the cast
to the proper type is lost and we only see a char *vpp. We then use that type
to create a temporary and we end up with a reg:QI rather than a reg:OO.
Is the casted pointer type supposed to be stripped away like that?
Anyway, I can work around that since I know what the temporary type should be
rather than stealing the type from the src operand.
next parent reply other threads:[~2022-08-26 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-101322-4@http.gcc.gnu.org/bugzilla/>
2022-08-26 19:15 ` bergner at gcc dot gnu.org [this message]
2022-09-01 2:17 ` cvs-commit at gcc dot gnu.org
2022-09-03 1:50 ` cvs-commit at gcc dot gnu.org
2022-09-12 17:40 ` cvs-commit at gcc dot gnu.org
2022-09-13 22:26 ` cvs-commit at gcc dot gnu.org
2022-09-13 22:27 ` bergner 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-101322-4-yeuWru12A0@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).