public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/62283] basic-block vectorization fails
Date: Mon, 01 Sep 2014 13:35:00 -0000 [thread overview]
Message-ID: <bug-62283-4-HtdgTzVFeA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62283-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62283
--- Comment #11 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 1 Sep 2014, ro at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62283
>
> Rainer Orth <ro at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |ro at gcc dot gnu.org
>
> --- Comment #10 from Rainer Orth <ro at gcc dot gnu.org> ---
> The last patch introduced a failure on SPARC:
>
> FAIL: gcc.dg/vect/vect-33.c scan-tree-dump-times vect "Alignment of access
> forced using versioning" 1
> FAIL: gcc.dg/vect/vect-33.c -flto -ffat-lto-objects scan-tree-dump-times vect
> "Alignment of access forced using versioning" 1
>
> The vect dump still says
>
> note: Alignment of access forced using peeling.
Can you attach the vect dump? I suppose vectors are rather short on
SPARC?
next prev parent reply other threads:[~2014-09-01 13:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 11:49 [Bug fortran/62283] New: SSE optimization fails holst at matmech dot com
2014-08-27 11:52 ` [Bug fortran/62283] " holst at matmech dot com
2014-08-27 12:00 ` [Bug fortran/62283] basic-block vectorization fails rguenth at gcc dot gnu.org
2014-08-27 12:43 ` rguenth at gcc dot gnu.org
2014-08-27 14:26 ` holst at matmech dot com
2014-08-27 14:52 ` holst at matmech dot com
2014-08-28 9:17 ` rguenth at gcc dot gnu.org
2014-08-28 9:42 ` rguenth at gcc dot gnu.org
2014-08-28 13:14 ` rguenth at gcc dot gnu.org
2014-08-28 13:14 ` rguenth at gcc dot gnu.org
2014-09-01 13:33 ` ro at gcc dot gnu.org
2014-09-01 13:35 ` rguenther at suse dot de [this message]
2014-09-01 13:37 ` ro at gcc dot gnu.org
2014-09-01 14:11 ` rguenth at gcc dot gnu.org
2014-09-01 14:29 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-09-01 14:41 ` rguenther at suse dot de
2014-09-02 11:08 ` ro at gcc dot gnu.org
2014-09-02 11:08 ` ro at gcc dot gnu.org
2014-09-02 11:12 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-09-02 12:11 ` rguenth at gcc dot gnu.org
2014-09-02 12:17 ` rguenth at gcc dot gnu.org
2015-04-28 8:31 ` rguenth at gcc dot gnu.org
2015-04-28 8:32 ` rguenth at gcc dot gnu.org
2015-05-04 14:43 ` ro at gcc dot gnu.org
2015-05-04 14:44 ` ro at gcc dot gnu.org
2015-05-06 6:47 ` rguenth at gcc dot gnu.org
2015-05-06 6:48 ` rguenth at gcc dot gnu.org
2015-05-06 6:48 ` rguenth at gcc dot gnu.org
2015-05-06 11:31 ` ro at gcc dot gnu.org
2015-05-06 12:18 ` rguenther at suse dot de
2015-05-06 12:21 ` rguenth at gcc dot gnu.org
2024-02-28 14:59 ` ro at gcc dot gnu.org
2024-02-28 15:01 ` ro at gcc dot gnu.org
2024-03-15 21:27 ` anlauf at gcc dot gnu.org
2024-03-15 21:41 ` [Bug tree-optimization/62283] " 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-62283-4-HtdgTzVFeA@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).