public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: Ian Bolton <ian.bolton@arm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, ARM] Suppress Redundant Flag Setting for Cortex-A15
Date: Tue, 28 Jan 2014 12:10:00 -0000	[thread overview]
Message-ID: <CAJA7tRYw7+4+RbeD+ugiQj7NbKxsgxSUk4XtCdeAyjxG4++0XA@mail.gmail.com> (raw)
In-Reply-To: <52e2a013.89e8440a.49e1.fffffee3SMTPIN_ADDED_BROKEN@mx.google.com>

On Fri, Jan 24, 2014 at 5:16 PM, Ian Bolton <ian.bolton@arm.com> wrote:
> Hi there!
>
> An existing optimisation for Thumb-2 converts t32 encodings to
> t16 encodings to reduce codesize, at the expense of causing
> redundant flag setting for ADD, AND, etc.  This redundant flag
> setting can have negative performance impact on cortex-a15.
>
> This patch introduces two new tuning options so that the conversion
> from t32 to t16, which takes place in thumb2_reorg, can be suppressed
> for cortex-a15.
>
> To maintain some of the original benefit (reduced codesize), the
> suppression is only done where the enclosing basic block is deemed
> worthy of optimising for speed.
>
> This tested with no regressions and performance has improved for
> the workloads tested on cortex-a15.  (It might be beneficial to
> other processors too, but that has not been investigated yet.)
>
> OK for stage 1?

This is OK for stage1.

Ramana

>
> Cheers,
> Ian
>
>
> 2014-01-24  Ian Bolton  <ian.bolton@arm.com>
>
> gcc/
>         * config/arm/arm-protos.h (tune_params): New struct members.
>         * config/arm/arm.c: Initialise tune_params per processor.
>         (thumb2_reorg): Suppress conversion from t32 to t16 when
>         optimizing for speed, based on new tune_params.

       reply	other threads:[~2014-01-28 12:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52e2a013.89e8440a.49e1.fffffee3SMTPIN_ADDED_BROKEN@mx.google.com>
2014-01-28 12:10 ` Ramana Radhakrishnan [this message]
2014-04-23 12:51   ` Christophe Lyon
2014-04-24 17:24     ` Ian Bolton
2014-01-24 17:16 Ian Bolton

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=CAJA7tRYw7+4+RbeD+ugiQj7NbKxsgxSUk4XtCdeAyjxG4++0XA@mail.gmail.com \
    --to=ramana.gcc@googlemail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ian.bolton@arm.com \
    --cc=ramrad01@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).