From: Steve Ellcey <sellcey@cavium.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Cc: Richard Biener <richard.guenther@gmail.com>,
rdapp <rdapp@linux.vnet.ibm.com>
Subject: Re: [PATCH] Fix fortran vector tests on powerpc and aarch64, PR tree-optimization/80925
Date: Tue, 12 Sep 2017 17:34:00 -0000 [thread overview]
Message-ID: <1505237660.2286.4.camel@cavium.com> (raw)
In-Reply-To: <1503679563.28672.111.camel@cavium.com>
Ping,  also adding fortran@gcc.gnu.org which I seem to left out when
sending this to gcc-patches@gcc.gnu.org.
Steve
On Fri, 2017-08-25 at 09:46 -0700, Steve Ellcey wrote:
> My earlier patch to update tests and resolve PR tree-
> optimization/80925
> did not include FORTRAN, just C and C++.  This patch makes the same
> changes as the earlier patches but for FORTRAN.  Tested on aarch64.
>
> OK to checkin?
>
> Steve Ellcey
> sellcey@cavium.com
>
> Orginal patches/discussion is at:
>
> https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01862.html
> https://gcc.gnu.org/ml/gcc-patches/2017-08/msg00000.html
>
>
> 2017-08-25  Steve Ellcey  <sellcey@cavium.com>
>
> Â Â Â Â Â Â Â Â PR tree-optimization/80925
> Â Â Â Â Â Â Â Â * gfortran.dg/vect/vect-2.f90: Add
> Â Â Â Â Â Â Â Â --param vect-max-peeling-for-alignment=0 option.
> Â Â Â Â Â Â Â Â Remove unaligned access and peeling checks.
> Â Â Â Â Â Â Â Â * gfortran.dg/vect/vect-3.f90: Ditto.
> Â Â Â Â Â Â Â Â * gfortran.dg/vect/vect-4.f90: Ditto.
> Â Â Â Â Â Â Â Â * gfortran.dg/vect/vect-5.f90: Ditto.
>
next parent reply other threads:[~2017-09-12 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1503679563.28672.111.camel@cavium.com>
2017-09-12 17:34 ` Steve Ellcey [this message]
2017-09-12 18:12 ` Paul Richard Thomas
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=1505237660.2286.4.camel@cavium.com \
--to=sellcey@cavium.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdapp@linux.vnet.ibm.com \
--cc=richard.guenther@gmail.com \
/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).