public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104112] [12 Regression] ICE with -Ofast -march=armv8.2-a+sve -msve-vector-bits=512 since r12-2292-g1dd3f21095858fbfd3e28a149578d5fb67e75f95
Date: Wed, 19 Jan 2022 11:13:55 +0000	[thread overview]
Message-ID: <bug-104112-4-KUXxgt5s2h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104112-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the issue is we hit

vect_create_partial_epilog (tree vec_def, tree vectype, code_helper code,
                            gimple_seq *seq)
{
  unsigned nunits = TYPE_VECTOR_SUBPARTS (TREE_TYPE (vec_def)).to_constant ();
  unsigned nunits1 = TYPE_VECTOR_SUBPARTS (vectype).to_constant ();
  tree stype = TREE_TYPE (vectype);
  tree new_temp = vec_def;
  while (nunits > nunits1)
    {
      nunits /= 2;
      tree vectype1 = get_related_vectype_for_scalar_type (TYPE_MODE (vectype),
                                                           stype, nunits);
      unsigned int bitsize = tree_to_uhwi (TYPE_SIZE (vectype1));

with

(gdb) p debug_generic_expr (vectype)
vector(2) double
$3 = void
(gdb) p debug_generic_expr (vec_def->typed.type)
vector(8) double

but when looking for a nunits == 4 vectype we end up with no valid vector type.
returned from get_related_vectype_for_scalar_type.

The code that checks whether we can vectorize doesn't verify that such
modes exist, that would need to be added.  But maybe the above isn't
exactly the correct way to get at it?  Do the command-line options
really disable V4DFmode support?

  parent reply	other threads:[~2022-01-19 11:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19  8:21 [Bug target/104112] New: ICE with -Ofast -march=armv8.2-a+sve -msve-vector-bits=512 gilles.gouaillardet at gmail dot com
2022-01-19  8:23 ` [Bug target/104112] " gilles.gouaillardet at gmail dot com
2022-01-19  8:52 ` [Bug target/104112] [12 Regression] ICE with -Ofast -march=armv8.2-a+sve -msve-vector-bits=512 since r12-2292-g1dd3f21095858fbfd3e28a149578d5fb67e75f95 marxin at gcc dot gnu.org
2022-01-19 10:58 ` [Bug tree-optimization/104112] " rguenth at gcc dot gnu.org
2022-01-19 11:13 ` rguenth at gcc dot gnu.org [this message]
2022-01-19 11:15 ` rguenth at gcc dot gnu.org
2022-01-19 11:29 ` rguenth at gcc dot gnu.org
2022-01-19 11:34 ` rguenth at gcc dot gnu.org
2022-01-19 11:57 ` rguenth at gcc dot gnu.org
2022-01-19 12:11 ` rsandifo at gcc dot gnu.org
2022-01-19 12:12 ` rguenth at gcc dot gnu.org
2022-01-19 12:43 ` rguenth at gcc dot gnu.org
2022-01-19 13:55 ` cvs-commit at gcc dot gnu.org
2022-01-19 13:55 ` 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-104112-4-KUXxgt5s2h@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).