From: Uros Bizjak <ubizjak@gmail.com>
To: Yulia Koval <vaalfreja@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH] Tune for lakemont
Date: Thu, 01 Oct 2015 12:43:00 -0000 [thread overview]
Message-ID: <CAFULd4Y9_Me_bq6d=DdhcrJ1biNgUhCkOD40P19WzQiHfUw7EA@mail.gmail.com> (raw)
In-Reply-To: <CAE0nxxjb=nUAuHt28Nt_CNq=7h0BSXT5bgm2i=iopaYc7DpODw@mail.gmail.com>
On Thu, Oct 1, 2015 at 2:37 PM, Yulia Koval <vaalfreja@gmail.com> wrote:
> Hi,
>
> The patch below contains some tuning changes for Lakemont, introduced
> by H.J. Lu. Bootstraped/regtested for Linux/x86_64. Ok for trunk?
>
> * gcc/config/i386/x86-tune.def (X86_TUNE_USE_BT): Enable
> for Lakemont.
> (X86_TUNE_ZERO_EXTEND_WITH_AND): Disable for Lakemont.
Non-algorithmic tuning of various parameters, especially the ones in
x86-tune.def, is always OK and pre-approved as an "obvious" patch.
Thanks,
Uros.
next prev parent reply other threads:[~2015-10-01 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 12:37 Yulia Koval
2015-10-01 12:43 ` Uros Bizjak [this message]
2015-10-01 13:37 ` H.J. Lu
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='CAFULd4Y9_Me_bq6d=DdhcrJ1biNgUhCkOD40P19WzQiHfUw7EA@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=vaalfreja@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).