public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52865] GCC can't vectorize fortran loop but able to vectorize similar c-loop
Date: Wed, 16 Jan 2013 11:32:00 -0000 [thread overview]
Message-ID: <bug-52865-4-vVPg68GEot@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52865-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52865
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #11 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-01-16 11:32:15 UTC ---
(In reply to comment #8)
> In another bug I stated that
See PR 53957
next prev parent reply other threads:[~2013-01-16 11:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 13:26 [Bug fortran/52865] New: " izamyatin at gmail dot com
2012-04-04 13:27 ` [Bug fortran/52865] " izamyatin at gmail dot com
2012-04-04 13:50 ` rguenth at gcc dot gnu.org
2012-04-04 14:00 ` [Bug tree-optimization/52865] " burnus at gcc dot gnu.org
2012-04-04 14:26 ` burnus at gcc dot gnu.org
2012-04-04 15:20 ` izamyatin at gmail dot com
2012-04-16 7:17 ` izamyatin at gmail dot com
2013-01-16 7:02 ` [Bug fortran/52865] " izamyatin at gmail dot com
2013-01-16 10:04 ` rguenth at gcc dot gnu.org
2013-01-16 10:26 ` jakub at gcc dot gnu.org
2013-01-16 10:47 ` jakub at gcc dot gnu.org
2013-01-16 11:32 ` burnus at gcc dot gnu.org [this message]
2013-01-16 11:59 ` jakub at gcc dot gnu.org
2013-01-16 16:06 ` jakub at gcc dot gnu.org
2013-01-16 22:27 ` steven at gcc dot gnu.org
2013-03-28 13:24 ` 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-52865-4-vVPg68GEot@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).