From: Uros Bizjak <ubizjak@gmail.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Vladimir Makarov <vmakarov@redhat.com>,
Hongtao Liu <crazylht@gmail.com>
Subject: Re: [PATCH] i386: Disable param ira-consider-dup-in-all-alts [PR100328]
Date: Fri, 2 Jul 2021 10:05:57 +0200 [thread overview]
Message-ID: <CAFULd4aG3=x+wRMr35+zO8TfSoBKKpGfs=M39i8PZY7s7kz2yQ@mail.gmail.com> (raw)
In-Reply-To: <1f49b5b4-51a0-2695-c797-233d3ffe73c0@linux.ibm.com>
On Fri, Jul 2, 2021 at 4:28 AM Kewen.Lin <linkw@linux.ibm.com> wrote:
>
> Hi,
>
> With Hongtao's help (thanks), we got the SPEC2017 performance
> evaluation result on x86_64 (see [1]), this new parameter
> ira-consider-dup-in-all-alts has negative effects on i386.
> Since we observed it can benefit ports aarch64 and rs6000, the
> param is set as 1 by default, this patch is to disable it on
> i386 explicitly to avoid performance degradation there.
>
> Bootstrapped & regtested on x86_64-redhat-linux.
>
> Is it ok for trunk?
OK.
Thanks,
Uros.
next prev parent reply other threads:[~2021-07-02 8:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 5:18 [RFC/PATCH] ira: Consider matching constraints with param [PR100328] Kewen.Lin
2021-06-28 6:26 ` [RFC/PATCH v3] ira: Support more matching constraint forms " Kewen.Lin
2021-06-28 7:12 ` Hongtao Liu
2021-06-28 7:20 ` Hongtao Liu
2021-06-28 7:27 ` Kewen.Lin
2021-06-30 8:53 ` Hongtao Liu
2021-06-30 9:42 ` Kewen.Lin
2021-06-30 10:18 ` Hongtao Liu
2021-06-30 15:42 ` Richard Sandiford
2021-07-02 2:18 ` Kewen.Lin
2021-06-30 15:24 ` Vladimir Makarov
2021-07-02 2:11 ` [PATCH v4] " Kewen.Lin
2021-07-02 2:28 ` [PATCH] i386: Disable param ira-consider-dup-in-all-alts [PR100328] Kewen.Lin
2021-07-02 8:05 ` Uros Bizjak [this message]
2021-07-05 13:04 ` [PATCH v4] ira: Support more matching constraint forms with param [PR100328] Vladimir Makarov
2021-06-30 15:25 ` [RFC/PATCH v3] " Vladimir Makarov
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='CAFULd4aG3=x+wRMr35+zO8TfSoBKKpGfs=M39i8PZY7s7kz2yQ@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=vmakarov@redhat.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).