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 testsuite/105486] new test case gcc.dg/vect/bb-slp-pr104240.c from r13-71-g41e3db05d69740
Date: Thu, 05 May 2022 07:16:19 +0000 [thread overview]
Message-ID: <bug-105486-4-TYs3kGrNvf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105486-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105486
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|sayle at gcc dot gnu.org |rguenth at gcc dot gnu.org
Summary|new test case |new test case
|gcc.dg/vect/bb-slp-pr104240 |gcc.dg/vect/bb-slp-pr104240
|.c from |.c from
|r13-89-gb3e98eb3396e16 |r13-71-g41e3db05d69740
|fails |
Version|12.0 |13.0
Ever confirmed|0 |1
Keywords| |testsuite-fail
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2022-05-05
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
The testcase is from my r13-71-g41e3db05d69740. Can you attach the slp2 dump
file please? I suspect we're missing vect_hw_misalign support checking
(but altering the testcase to use __builtin_assume_alignment () on all args
should work as well).
Can you check?
next prev parent reply other threads:[~2022-05-05 7:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 21:07 [Bug testsuite/105486] New: new test case gcc.dg/vect/bb-slp-pr104240.c from r13-89-gb3e98eb3396e16 fails seurer at gcc dot gnu.org
2022-05-05 7:16 ` rguenth at gcc dot gnu.org [this message]
2022-05-05 8:42 ` [Bug testsuite/105486] new test case gcc.dg/vect/bb-slp-pr104240.c from r13-71-g41e3db05d69740 cvs-commit at gcc dot gnu.org
2022-05-05 8:43 ` rguenth at gcc dot gnu.org
2022-05-05 10:08 ` roger at nextmovesoftware dot com
2022-05-05 12:31 ` cvs-commit at gcc dot gnu.org
2022-05-07 20:04 ` roger at nextmovesoftware dot com
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-105486-4-TYs3kGrNvf@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).