public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch AArch64 4/4] Add -moverride tuning command, and wire it up for control of fusion and fma-steering
Date: Fri, 26 Jun 2015 12:52:00 -0000	[thread overview]
Message-ID: <CAFqB+PyCy1=8X4yhwztFm1S=3E4=90eqwK_feChP2y6s06j9mg@mail.gmail.com> (raw)
In-Reply-To: <1435049360-10990-5-git-send-email-james.greenhalgh@arm.com>

On 23 June 2015 at 09:49, James Greenhalgh <james.greenhalgh@arm.com> wrote:
>
> Hi,
>
> This final patch adds support for the new command line option
> "-moverride". The purpose of this command line is to allow expert-level users
> of the compiler, and those comfortable with experimenting with the compiler,
> *unsupported* full access to the tuning structures used in the AArch64
> back-end.
>
> For now, we only enable command-line access to the fusion pairs to
> enable and whether or not to use the Cortex-A57 FMA register renaming
> pass. Though in future we can expand this further.
>
> With this patch, you might write something like:
>
>   -moverride=fuse=adrp+add.cmp+branch:tune=rename_fma_regs
>
> To enable fusion of adrp+add and cmp+branch and to enable the
> fma-rename pass.
>
> I've bootstrapped and tested the patch set on aarch64-none-linux-gnu
> with BOOT_CFLAGS set to the example string above, and again in the
> standard configuration with no issues.
>
> OK?
>
> Thanks,
> James
>
> ---
> 2015-06-23  James Greenhalgh  <james.greenhalgh@arm.com>
>
>         * config/aarch64/aarch64.opt: (override): New.
>         * doc/invoke.texi (override): Document.
>         * config/aarch64/aarch64.c (aarch64_flag_desc): New
>         (aarch64_fusible_pairs): Likewise.
>         (aarch64_tuning_flags): Likewise.
>         (aarch64_tuning_override_function): Likewise.
>         (aarch64_tuning_override_functions): Likewise.
>         (aarch64_parse_one_option_token): Likewise.
>         (aarch64_parse_boolean_options): Likewise.
>         (aarch64_parse_fuse_string): Likewise.
>         (aarch64_parse_tune_string): Likewise.
>         (aarch64_parse_one_override_token): Likewise.
>         (aarch64_parse_override_string): Likewise.
>         (aarch64_override_options): Parse the -override string if it
>         is present.
>

+static const struct aarch64_tuning_override_function
+  aarch64_tuning_override_functions[] =

The indentation looks odd here, but otherwise OK /Marcus

      reply	other threads:[~2015-06-26 12:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  8:49 [Patch AArch64 0/4] Add "-moverride" option for overriding tuning parameters James Greenhalgh
2015-06-23  8:49 ` [Patch AArch64 2/4] Control the FMA steering pass in tuning structures rather than as core property James Greenhalgh
2015-06-26 12:41   ` Marcus Shawcroft
2015-06-23  8:50 ` [Patch AArch64 3/4] De-const-ify struct tune_params James Greenhalgh
2015-06-26 12:44   ` Marcus Shawcroft
2015-06-23  8:50 ` [Patch AArch64 1/4] Define candidates for instruction fusion in a .def file James Greenhalgh
2015-06-26 12:41   ` Marcus Shawcroft
2015-06-23  8:52 ` [Patch AArch64 4/4] Add -moverride tuning command, and wire it up for control of fusion and fma-steering James Greenhalgh
2015-06-26 12:52   ` Marcus Shawcroft [this message]

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='CAFqB+PyCy1=8X4yhwztFm1S=3E4=90eqwK_feChP2y6s06j9mg@mail.gmail.com' \
    --to=marcus.shawcroft@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=james.greenhalgh@arm.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).