public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104445] [12 Regression] ICE in vect_create_partial_epilog, at tree-vect-loop.cc:5098
Date: Wed, 09 Feb 2022 10:01:05 +0000	[thread overview]
Message-ID: <bug-104445-4-qXzV0UgO2B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104445-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Uroš Bizjak <ubizjak at gmail dot com> ---
We do have:

(define_expand "vec_extractv4qiqi"
  [(match_operand:QI 0 "register_operand")
   (match_operand:V4QI 1 "register_operand")
   (match_operand 2 "const_int_operand")]
  "TARGET_SSE4_1"
{
  ix86_expand_vector_extract (false, operands[0],
                              operands[1], INTVAL (operands[2]));
  DONE;
})

  parent reply	other threads:[~2022-02-09 10:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 19:39 [Bug c/104445] New: " gscfq@t-online.de
2022-02-08 20:48 ` [Bug tree-optimization/104445] " pinskia at gcc dot gnu.org
2022-02-09  5:45 ` pinskia at gcc dot gnu.org
2022-02-09  5:48 ` pinskia at gcc dot gnu.org
2022-02-09  7:31 ` rguenth at gcc dot gnu.org
2022-02-09  9:55 ` rguenth at gcc dot gnu.org
2022-02-09 10:01 ` ubizjak at gmail dot com [this message]
2022-02-09 10:21 ` rguenth at gcc dot gnu.org
2022-02-09 10:26 ` ubizjak at gmail dot com
2022-02-09 10:48 ` rguenther at suse dot de
2022-02-09 10:59 ` ubizjak at gmail dot com
2022-02-09 11:33 ` rguenth at gcc dot gnu.org
2022-02-09 13:03 ` cvs-commit at gcc dot gnu.org
2022-02-09 13:03 ` 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-104445-4-qXzV0UgO2B@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).