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 target/78643] [6 Regression] ICE in convert_move, at expr.c:230
Date: Tue, 25 Oct 2022 17:31:14 +0000	[thread overview]
Message-ID: <bug-78643-4-lqiVxi8hck@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-78643-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78643

--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

https://gcc.gnu.org/g:1c64aba8cdf6509533f554ad86640f274cdbe37f

commit r13-3490-g1c64aba8cdf6509533f554ad86640f274cdbe37f
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Wed Oct 19 12:53:35 2022 -0700

    Always use TYPE_MODE instead of DECL_MODE for vector field

    e034c5c8957 re PR target/78643 (ICE in convert_move, at expr.c:230)

    fixed the case where DECL_MODE of a vector field is BLKmode and its
    TYPE_MODE is a vector mode because of target attribute.  Remove the
    BLKmode check for the case where DECL_MODE of a vector field is a vector
    mode and its TYPE_MODE isn't a vector mode because of target attribute.

    gcc/

            PR target/107304
            * expr.cc (get_inner_reference): Always use TYPE_MODE for vector
            field with vector raw mode.

    gcc/testsuite/

            PR target/107304
            * gcc.target/i386/pr107304.c: New test.

       reply	other threads:[~2022-10-25 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-78643-4@http.gcc.gnu.org/bugzilla/>
2022-10-25 17:31 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-08 21:22 ` cvs-commit at gcc dot gnu.org
2022-11-08 21:56 ` cvs-commit at gcc dot gnu.org
2022-11-08 22:25 ` cvs-commit 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-78643-4-lqiVxi8hck@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).