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/106887] ICE in extract_insn, at recog.cc:2791 since r13-2111-g6910cad55ffc330d
Date: Tue, 20 Sep 2022 01:30:04 +0000	[thread overview]
Message-ID: <bug-106887-4-OwtqofsdUd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106887-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kong Lingling <konglin1@gcc.gnu.org>:

https://gcc.gnu.org/g:78260b9a9c0bf5a4495320466e2cd1c259504905

commit r13-2725-g78260b9a9c0bf5a4495320466e2cd1c259504905
Author: konglin1 <lingling.kong@intel.com>
Date:   Fri Sep 16 15:59:19 2022 +0800

    i386: Fixed vec_init_dup_v16bf [PR106887]

    gcc/ChangeLog:

            PR target/106887
            * config/i386/i386-expand.cc (ix86_expand_vector_init_duplicate):
            Fixed V16BF mode case.

    gcc/testsuite/ChangeLog:

            PR target/106887
            * gcc.target/i386/vect-bfloat16-2c.c: New test.

  parent reply	other threads:[~2022-09-20  1:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  8:42 [Bug target/106887] New: " marxin at gcc dot gnu.org
2022-09-08  8:42 ` [Bug target/106887] " marxin at gcc dot gnu.org
2022-09-15  2:25 ` asolokha at gmx dot com
2022-09-20  1:30 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-26  6:56 ` rguenth at gcc dot gnu.org
2023-05-11 14:11 ` jamborm at gcc dot gnu.org
2023-05-30 13:12 ` jamborm 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-106887-4-OwtqofsdUd@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).