public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/95058] [11 regression] vector test case failures starting with r11-205
Date: Mon, 11 May 2020 15:23:15 +0000 [thread overview]
Message-ID: <bug-95058-4-jTe2qypbHJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95058-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95058
--- Comment #4 from Bill Seurer <seurer at linux dot vnet.ibm.com> ---
And for the power 7 specific one (the other one also occurs on power 7)
Executing on host: /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/vect/bb-slp-pr69907.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -flto -ffat-lto-objects
-maltivec -mvsx -mno-allow-movmisalign -ftree-vectorize
-fno-tree-loop-distribute-patterns -fno-vect-cost-model -fno-common -O2
-fdump-tree-slp-details -O3 -S -o bb-slp-pr69907.s (timeout = 300)
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/vect/bb-slp-pr69907.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -flto -ffat-lto-objects
-maltivec -mvsx -mno-allow-movmisalign -ftree-vectorize
-fno-tree-loop-distribute-patterns -fno-vect-cost-model -fno-common -O2
-fdump-tree-slp-details -O3 -S -o bb-slp-pr69907.s
PASS: gcc.dg/vect/bb-slp-pr69907.c -flto -ffat-lto-objects (test for excess
errors)
FAIL: gcc.dg/vect/bb-slp-pr69907.c -flto -ffat-lto-objects scan-tree-dump slp1
"BB vectorization with gaps at the end of a load is not supported"
next prev parent reply other threads:[~2020-05-11 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 13:01 [Bug other/95058] New: " seurer at linux dot vnet.ibm.com
2020-05-11 13:04 ` [Bug tree-optimization/95058] " rguenth at gcc dot gnu.org
2020-05-11 15:17 ` seurer at linux dot vnet.ibm.com
2020-05-11 15:19 ` seurer at linux dot vnet.ibm.com
2020-05-11 15:23 ` seurer at linux dot vnet.ibm.com [this message]
2020-05-11 15:23 ` seurer at linux dot vnet.ibm.com
2020-05-12 12:28 ` rguenth at gcc dot gnu.org
2020-05-25 14:04 ` rguenth at gcc dot gnu.org
2020-05-25 14:09 ` rguenth at gcc dot gnu.org
2020-05-26 15:33 ` seurer at linux dot vnet.ibm.com
2020-06-03 2:49 ` seurer at linux dot vnet.ibm.com
2020-07-08 6:54 ` 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-95058-4-jTe2qypbHJ@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).