public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102516] [12 regression] pr65947-13.c and vect-alias-check-18.c fail on armeb since r12-3893
Date: Tue, 12 Apr 2022 15:31:52 +0000 [thread overview]
Message-ID: <bug-102516-4-BMCuYitUAB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102516-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102516
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
I can reproduce this on an normal arm-eabi cross compiler with
$build/gcc/xgcc -B$build/gcc/ $src/gcc/testsuite/gcc.dg/vect/pr65947-13.c
-mbig-endian -march=armv7-a+simd -fdiagnostics-plain-output -mfloat-abi=softfp
-ffast-math -ftree-vectorize -fno-tree-loop-distribute-patterns
-fno-vect-cost-model -fno-common -O2 -fdump-tree-vect-details --param
vect-epilogues-nomask=0 -S -isystem
$build/arm-eabi/thumb/v7-a/nofp/newlib/targ-include -isystem
$src/newlib/libc/include -o pr65947-13.s
The test expects "LOOP VECTORIZED" to appear twice in the dump file, but it
only appears once.
next prev parent reply other threads:[~2022-04-12 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 15:00 [Bug middle-end/102516] New: " clyon at gcc dot gnu.org
2021-09-29 6:13 ` [Bug tree-optimization/102516] " rguenth at gcc dot gnu.org
2021-09-29 12:44 ` rguenth at gcc dot gnu.org
2021-09-29 13:12 ` clyon at gcc dot gnu.org
2022-04-12 15:31 ` rearnsha at gcc dot gnu.org [this message]
2022-04-12 21:11 ` clyon at gcc dot gnu.org
2022-05-06 8:31 ` [Bug tree-optimization/102516] [12/13 " jakub at gcc dot gnu.org
2022-10-19 9:34 ` rguenth at gcc dot gnu.org
2022-10-24 12:56 ` clyon at gcc dot gnu.org
2023-02-21 15:04 ` 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-102516-4-BMCuYitUAB@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).