From: Richard Biener <richard.guenther@gmail.com>
To: Robin Dapp <rdapp@linux.vnet.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"Bin.Cheng" <amker.cheng@gmail.com>,
Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/5 v3] Vect peeling cost model
Date: Wed, 24 May 2017 07:51:00 -0000 [thread overview]
Message-ID: <CAFiYyc2z1J-F6h+4gv9BKPx8Xn7AATz1qwrZ6r0-KPDTDZ+5ww@mail.gmail.com> (raw)
In-Reply-To: <279040cf-a300-ee84-d8f3-514d5405ea9a@linux.vnet.ibm.com>
On Tue, May 23, 2017 at 5:57 PM, Robin Dapp <rdapp@linux.vnet.ibm.com> wrote:
> The last version of the patch series caused some regressions for ppc64.
> This was largely due to incorrect handling of unsupportable alignment
> and should be fixed with the new version.
>
> p2 and p5 have not changed but I'm posting the whole series again for
> reference. p1 only changed comment wording, p3 was adapted to apply on
> the trunk.
>
> No regressions on s390x, x86-64 and ppc64. Bootstrapped.
So what did actually change? I'd rather not diff the diffs. Can you provide
an incremental change, aka p6 that would apply to the previous series instead?
Thanks,
Richard.
> Regards
> Robin
>
next prev parent reply other threads:[~2017-05-24 7:41 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 14:38 [RFC] S/390: Alignment peeling prolog generation Robin Dapp
2017-04-11 14:57 ` Bin.Cheng
2017-04-11 15:03 ` Robin Dapp
2017-04-11 15:07 ` Bin.Cheng
2017-04-11 16:25 ` Richard Biener
2017-04-12 7:51 ` Robin Dapp
2017-04-12 7:58 ` Richard Biener
2017-05-04 9:04 ` [PATCH 1/3] Vect peeling cost model Robin Dapp
2017-05-05 10:32 ` Richard Biener
2017-05-04 9:04 ` [RFC] S/390: Alignment peeling prolog generation Robin Dapp
2017-05-05 11:04 ` Richard Biener
2017-05-08 16:12 ` Robin Dapp
2017-05-09 10:38 ` Richard Biener
2017-05-11 11:17 ` [PATCH 1/5] Vect peeling cost model Robin Dapp
2017-05-11 11:17 ` [RFC] S/390: Alignment peeling prolog generation Robin Dapp
2017-05-11 12:15 ` Richard Biener
2017-05-11 12:16 ` Richard Biener
2017-05-11 12:48 ` Richard Biener
2017-05-11 11:18 ` [PATCH 2/5] Vect peeling cost model Robin Dapp
2017-05-11 11:19 ` [PATCH 3/5] " Robin Dapp
2017-05-11 11:20 ` [PATCH 4/5] " Robin Dapp
2017-05-11 15:30 ` [PATCH 4/5 v2] " Robin Dapp
2017-05-12 9:36 ` Richard Biener
2017-05-23 15:58 ` [PATCH 0/5 v3] " Robin Dapp
2017-05-24 7:51 ` Richard Biener [this message]
2017-05-24 11:57 ` Robin Dapp
2017-05-24 13:56 ` Richard Biener
2017-06-03 17:12 ` Andreas Schwab
2017-06-06 7:13 ` Robin Dapp
2017-06-06 17:26 ` Andreas Schwab
2017-06-07 10:50 ` Robin Dapp
2017-06-07 11:43 ` Andreas Schwab
2017-05-23 15:58 ` [PATCH 1/5 " Robin Dapp
2017-05-23 15:58 ` [PATCH 2/5 " Robin Dapp
2017-05-23 19:25 ` Richard Sandiford
2017-05-24 7:37 ` Robin Dapp
2017-05-24 7:53 ` Richard Sandiford
2017-05-23 15:59 ` [PATCH 5/5 " Robin Dapp
2017-05-23 15:59 ` [PATCH 4/5 " Robin Dapp
2017-05-31 13:56 ` Christophe Lyon
2017-05-31 14:37 ` Robin Dapp
2017-05-31 14:49 ` Christophe Lyon
2017-05-23 16:02 ` [PATCH 3/5 " Robin Dapp
2017-05-11 11:59 ` [PATCH 5/5] " Robin Dapp
2017-05-08 16:13 ` [PATCH 3/4] " Robin Dapp
2017-05-09 10:41 ` Richard Biener
2017-05-08 16:27 ` [PATCH 4/4] " Robin Dapp
2017-05-09 10:55 ` Richard Biener
2017-05-04 9:07 ` [PATCH 2/3] " Robin Dapp
2017-05-05 10:37 ` Richard Biener
2017-05-04 9:14 ` [PATCH 3/3] " Robin Dapp
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=CAFiYyc2z1J-F6h+4gv9BKPx8Xn7AATz1qwrZ6r0-KPDTDZ+5ww@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=amker.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=krebbel@linux.vnet.ibm.com \
--cc=rdapp@linux.vnet.ibm.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).