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 target/95969] Use of __builtin_aarch64_im_lane_boundsi in AArch64 arm_neon.h interferes with gimple optimisation
Date: Thu, 02 Sep 2021 20:51:56 +0000 [thread overview]
Message-ID: <bug-95969-4-k25zf0oGwc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95969-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95969
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Testcases that fail:
gcc.target/aarch64/vmov_n_1.c
at -O1:t.c: In function ‘test_vmov_n_f32’:
t.c:165:10: error: missing definition
for SSA_NAME: .MEM_161 in statement:
# VUSE <.MEM_161>
_162 = BIT_FIELD_REF <__a, 32, 0>;
during GIMPLE pass: cunroll
0xfdd233 verify_ssa(bool, bool)
/home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/tree-ssa.c:1214
0xf092ab verify_loop_closed_ssa(bool, loop*)
/home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/tree-ssa-loop-manip.c:766
0xf092ab verify_loop_closed_ssa(bool, loop*)
/home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/tree-ssa-loop-manip.c:760
0xeeeed3 tree_unroll_loops_completely
/home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/tree-ssa-loop-ivcanon.c:1498
0xeeef97 execute
/home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/tree-ssa-loop-ivcanon.c:1602
0xeeef97 execute
/home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/tree-ssa-loop-ivcanon.c:1592
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
at -O2+:
t.c: In function ‘test_vmov_n_f64’:
t.c:356:1: error: missing definition
356 | }
| ^
for SSA_NAME: .MEM_129 in statement:
# .MEM_131 = VDEF <.MEM_129>
__a ={v} {CLOBBER};
during GIMPLE pass: evrp
t.c:356:1: internal compiler error: verify_ssa failed
next prev parent reply other threads:[~2021-09-02 20:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 15:50 [Bug target/95969] New: " rsandifo at gcc dot gnu.org
2021-09-02 5:31 ` [Bug target/95969] " pinskia at gcc dot gnu.org
2021-09-02 5:32 ` pinskia at gcc dot gnu.org
2021-09-02 7:14 ` pinskia at gcc dot gnu.org
2021-09-02 8:28 ` ktkachov at gcc dot gnu.org
2021-09-02 8:37 ` pinskia at gcc dot gnu.org
2021-09-02 10:35 ` pinskia at gcc dot gnu.org
2021-09-02 20:51 ` pinskia at gcc dot gnu.org [this message]
2021-09-02 22:26 ` pinskia at gcc dot gnu.org
2021-09-13 15:19 ` cvs-commit at gcc dot gnu.org
2021-09-13 15:20 ` pinskia 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-95969-4-k25zf0oGwc@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).