From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [PATCH] Fix Fortran DO loop fallback
Date: Wed, 13 Jul 2016 10:32:00 -0000 [thread overview]
Message-ID: <CAFiYyc2oyJvzX-k2_qenHDNopRFd=4DQ8H7uyQ=RJ+pNt5Rbrg@mail.gmail.com> (raw)
In-Reply-To: <f4d7f51c-8e71-7ada-fb63-73934646006d@suse.cz>
On Tue, Jul 12, 2016 at 4:54 PM, Martin Liška <mliska@suse.cz> wrote:
> On 07/12/2016 03:15 PM, Richard Biener wrote:
>> The scan for 1 *n_ after FRE looks still useful. Btw, the testcase
>> doesn't fail for me,
>> we _do_ hoist the division in PRE, just not with -m32 anymore. Can
>> you confirm this?
>
> Yeah, it works for both -m32 and -m64.
> This is final version of the patch, may I install it?
Changelog has a swapped entry.
Ok with fixing that.
Richard.
> Thanks,
> Martin
next prev parent reply other threads:[~2016-07-13 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1467883947.git.mliska@suse.cz>
[not found] ` <CAFiYyc0FM93FwqjYOB+V2yn8b=g5xFL09U2xT0gaCOZLc4z3tA@mail.gmail.com>
[not found] ` <20160707144035.GA30837@kam.mff.cuni.cz>
[not found] ` <c1dd7016-53bc-0ff9-cb26-36054bfdbaaa@suse.cz>
[not found] ` <20160708084029.GZ7387@tucnak.redhat.com>
[not found] ` <20160708090334.GJ69430@kam.mff.cuni.cz>
2016-07-08 9:05 ` [PATCH 0/2, fortran] Better code generation for DO loops with +-1 step Jakub Jelinek
2016-07-08 9:13 ` FX
[not found] ` <86a3b430-0282-305b-8796-5a696d53b46a@suse.cz>
[not found] ` <9b6e6e1f-b62c-7ea4-1f72-417472fa96e4@redhat.com>
2016-07-11 15:24 ` [PATCH] Fix Fortran DO loop fallback Mike Stump
[not found] ` <CAFiYyc1sotqJVzpNaKiZ4azVsWxeouvZSRvMGXP98XStQrLDoA@mail.gmail.com>
2016-07-12 12:31 ` Martin Liška
2016-07-12 13:15 ` Richard Biener
2016-07-12 14:54 ` Martin Liška
2016-07-13 10:32 ` Richard Biener [this message]
2016-07-13 14:04 ` Martin Liška
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='CAFiYyc2oyJvzX-k2_qenHDNopRFd=4DQ8H7uyQ=RJ+pNt5Rbrg@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=mliska@suse.cz \
/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).