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/112623] [14 Regression] ICE: in emit_move_insn, at expr.cc:4249 with -O -mavx512vl -mavx512fp16 on vector conversion since r14-1707
Date: Tue, 21 Nov 2023 14:47:57 +0000	[thread overview]
Message-ID: <bug-112623-4-KBbbHGFjEd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112623-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:aef1aaff41190d2f82cf49d8907682b6dff71c3c

commit r14-5681-gaef1aaff41190d2f82cf49d8907682b6dff71c3c
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Nov 21 14:46:31 2023 +0100

    tree-optimization/112623 - forwprop VEC_PACK_TRUNC generation

    For vec_pack_trunc patterns there can be an ambiguity for the
    source mode for BFmode vs HFmode.  The vectorizer checks
    the insns operand mode for this, the following makes forwprop
    do the same.  That of course doesn't help if the target supports
    both conversions.

            PR tree-optimization/112623
            * tree-ssa-forwprop.cc (simplify_vector_constructor):
            Check the source mode of the insn for vector pack/unpacks.

            * gcc.target/i386/pr112623.c: New testcase.

  parent reply	other threads:[~2023-11-21 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19 16:43 [Bug target/112623] New: [14 Regression] ICE: in emit_move_insn, at expr.cc:4249 with -O -mavx512vl -mavx512fp16 on vector conversion zsojka at seznam dot cz
2023-11-20 10:35 ` [Bug target/112623] " rguenth at gcc dot gnu.org
2023-11-21 10:29 ` [Bug target/112623] [14 Regression] ICE: in emit_move_insn, at expr.cc:4249 with -O -mavx512vl -mavx512fp16 on vector conversion since r14-1707 jakub at gcc dot gnu.org
2023-11-21 11:09 ` jakub at gcc dot gnu.org
2023-11-21 11:56 ` rguenth at gcc dot gnu.org
2023-11-21 12:02 ` rguenth at gcc dot gnu.org
2023-11-21 12:13 ` rguenth at gcc dot gnu.org
2023-11-21 13:41 ` jakub at gcc dot gnu.org
2023-11-21 13:49 ` rguenth at gcc dot gnu.org
2023-11-21 14:47 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-21 14:48 ` 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-112623-4-KBbbHGFjEd@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).