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/112990] [14 Regression][s390x] ICE in related_vector_mode, at stor-layout.cc:539 since r14-3381-g27de9aa152141e
Date: Wed, 13 Dec 2023 08:43:38 +0000	[thread overview]
Message-ID: <bug-112990-4-wcuyFgyIeR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112990-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from GCC 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:b9baead90d74e9211fc94d655ecd5d3af3858158

commit r14-6482-gb9baead90d74e9211fc94d655ecd5d3af3858158
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Dec 13 09:38:59 2023 +0100

    tree-optimization/112990 - unsupported VEC_PERM from match pattern

    The following avoids creating an unsupported VEC_PERM after vector
    lowering from the pattern merging a bit-insert from a bit-field-ref
    to a VEC_PERM.  For the already existing s390 testcase we get
    TImode vectors which later ICE during attempted expansion of
    a vec_perm_const.

            PR tree-optimization/112990
            * match.pd (bit_insert @0 (BIT_FIELD_REF @1 ..) ..):
            Restrict to vector modes after lowering.

  parent reply	other threads:[~2023-12-13  8:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 20:54 [Bug target/112990] New: " mjires at suse dot cz
2023-12-12 21:51 ` [Bug target/112990] " pinskia at gcc dot gnu.org
2023-12-13  8:40 ` rguenth at gcc dot gnu.org
2023-12-13  8:43 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-13 11:50 ` 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-112990-4-wcuyFgyIeR@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).