public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/101294] [12 Regression] ICE: in maybe_legitimize_operand, at optabs.c:7614 with -mavx since r12-1958-gedafb35bdadf309e
Date: Fri, 02 Jul 2021 14:03:34 +0000	[thread overview]
Message-ID: <bug-101294-4-nMI7078Vrg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101294-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
This works:

diff --git a/gcc/expr.c b/gcc/expr.c
index 025033c9ecf..bd85bbfdd6f 100644
--- a/gcc/expr.c
+++ b/gcc/expr.c
@@ -7078,7 +7078,8 @@ store_constructor (tree exp, rtx target, int cleared,
poly_int64 size,
       && eltmode == GET_MODE_INNER (mode)
       && ((icode = optab_handler (vec_duplicate_optab, mode))
      != CODE_FOR_nothing)
-      && (elt = uniform_vector_p (exp)))
+      && (elt = uniform_vector_p (exp))
+      && !VECTOR_TYPE_P (TREE_TYPE (elt)))
     {
       class expand_operand ops[2];
       create_output_operand (&ops[0], target, mode);

  parent reply	other threads:[~2021-07-02 14:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  9:59 [Bug target/101294] New: [12 Regression] ICE: in maybe_legitimize_operand, at optabs.c:7614 with -mavx zsojka at seznam dot cz
2021-07-02 10:33 ` [Bug target/101294] [12 Regression] ICE: in maybe_legitimize_operand, at optabs.c:7614 with -mavx since r12-1958-gedafb35bdadf309e marxin at gcc dot gnu.org
2021-07-02 11:13 ` rguenth at gcc dot gnu.org
2021-07-02 13:04 ` [Bug middle-end/101294] " hjl.tools at gmail dot com
2021-07-02 14:03 ` hjl.tools at gmail dot com [this message]
2021-07-02 15:14 ` rguenther at suse dot de
2021-07-03 11:40 ` cvs-commit at gcc dot gnu.org
2021-07-03 11:41 ` hjl.tools at gmail dot com

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-101294-4-nMI7078Vrg@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).