public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103523] [11/12 Regression] SVE float auto-vect float format expand failure
Date: Thu, 02 Dec 2021 01:35:32 +0000 [thread overview]
Message-ID: <bug-103523-4-IZpfWqUihN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103523-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103523
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-12-02
Status|UNCONFIRMED |NEW
Component|target |tree-optimization
Ever confirmed|0 |1
Target Milestone|--- |11.3
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Tamar Christina from comment #1)
> An additional ICE seen on a month old tree is
> unsure if this was fixed or just hidden...
It is extra checking (that is --enable-checking vs --enable-checking=release):
504 gcc_checking_assert (is_constant ());
#7 0x000000000189d858 in nunits_for_known_piecewise_op (type=0xfffff5bc91b0)
at /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/tree-vect-generic.c:101
101 return TYPE_VECTOR_SUBPARTS (type).to_constant ();
(gdb) p type
$1 = (const_tree) 0xfffff5bc91b0
(gdb) p debug_generic_expr(type)
vector([2,2]) float
#10 0x00000000018a97a8 in expand_vector_operations_1 (gsi=0xfffffffff570,
dce_ssa_names=0xfffffffff588) at
/home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/tree-vect-generic.c:2331
(gdb) p code
$9 = MULT_EXPR
(gdb) p type
$10 = (tree) 0xfffff5bc91b0
(gdb) p debug_generic_expr(type)
vector([2,2]) float //E_VNx2SFmode
(gdb) p op
$12 = smul_optab
(gdb) p debug_generic_expr(compute_type)
float
(gdb) p debug_generic_expr(get_compute_type(code, op, type))
float
(gdb) p optab_handler(op, E_VNx2SFmode)
$23 = CODE_FOR_nothing
(gdb) p op
$24 = smul_optab
I don't know enough of the SVE backend to understand VNx2SF vs VNx4SF really
and why the vectorizer is chosing VNx2SF mode here which does not support half
of the instructions (according to the backend).
next prev parent reply other threads:[~2021-12-02 1:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 20:58 [Bug target/103523] New: [12 " tnfchris at gcc dot gnu.org
2021-12-01 21:19 ` [Bug target/103523] [11/12 " tnfchris at gcc dot gnu.org
2021-12-02 1:35 ` pinskia at gcc dot gnu.org [this message]
2021-12-02 1:48 ` [Bug tree-optimization/103523] " pinskia at gcc dot gnu.org
2021-12-02 10:57 ` rguenth at gcc dot gnu.org
2021-12-03 8:33 ` joelh at gcc dot gnu.org
2021-12-03 8:37 ` [Bug tree-optimization/103523] [11/12 Regression] SVE float auto-vect float format expand failure exposed by r11-7861-ge4180ab2f pinskia at gcc dot gnu.org
2021-12-06 12:10 ` tnfchris at gcc dot gnu.org
2021-12-10 10:28 ` [Bug tree-optimization/103523] [11/12 Regression] vectorizable_induction generating code for modes without checking support for them " cvs-commit at gcc dot gnu.org
2021-12-10 10:31 ` joelh at gcc dot gnu.org
2021-12-10 10:47 ` tnfchris at gcc dot gnu.org
2021-12-13 14:21 ` [Bug tree-optimization/103523] [11 " cvs-commit at gcc dot gnu.org
2021-12-15 9:28 ` joelh 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-103523-4-IZpfWqUihN@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).