From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <richard.earnshaw@arm.com>,
Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
Subject: Re: [ARM] Wire up the new scheduler description for the ARM Cortex-A57 processor
Date: Mon, 26 Jan 2015 09:14:00 -0000 [thread overview]
Message-ID: <CAJA7tRbwBQxqrw6hRW6ifpyAEuTTLY4AyF_2Do3QwRMCCwhuhw@mail.gmail.com> (raw)
In-Reply-To: <1421689467-4255-1-git-send-email-james.greenhalgh@arm.com>
On Mon, Jan 19, 2015 at 5:44 PM, James Greenhalgh
<james.greenhalgh@arm.com> wrote:
>
> On Fri, Jan 16, 2015 at 11:14:42AM +0000, Ramana Radhakrishnan wrote:
>>
>>
>> On 16/01/15 10:20, Marcus Shawcroft wrote:
>> > On 15 January 2015 at 09:50, James Greenhalgh <james.greenhalgh@arm.com> wrote:
>> >
>> >> 2015-01-15 James Greenhalgh <james.greenhalgh@arm.com>
>> >>
>> >> * config/arm/cortex-a57.md: New.
>> >> * config/aarch64/aarch64.md: Include it.
>> >> * config/aarch64/aarch64-cores.def (cortex-a57): Tune for it.
>> >> * config/aarch64/aarch64-tune.md: Regenerate.
>> >
>> > This is low risk and only affects aarch64 backend. I think we should
>> > take this for gcc 5, so OK.
>> >
>> > Ramana do you want this wired up for aarch32 in a followup?
>>
>> Yes please. I think as long as it works, let's just take it for 5.0. I'd
>> rather not have divergence between the backends as this just creates
>> problems for us elsewhere.
>
> Hi,
>
> OK, that patch looks like this. I know I've missed the stage 3 deadline,
> but I agree that the two back ends should not diverge too much - and
> this patch is small and gives a nice little boost to performance on
> some popular benchmarks.
>
> I've regression tested it over the weekend with no issues.
>
> OK?
This is OK as this is a tuning patch that was posted before the stage3
deadline and only wires in a pipeline description.
Ramana
>
> Cheers,
> James
>
> ---
> 2014-01-19 James Greenhalgh <james.greenhalgh@arm.com>
>
> * config/arm/arm-cores.def (cortex-a57): Use the new Cortex-A57
> pipeline model.
> config/arm/arm.md: Include the new Cortex-A57 model.
> (generic_sched): Don't use generic_sched when tuning for
> Cortex-A57.
next prev parent reply other threads:[~2015-01-26 8:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 10:48 [AArch64] Add a new scheduling " James Greenhalgh
2015-01-16 10:39 ` Marcus Shawcroft
2015-01-16 11:18 ` Ramana Radhakrishnan
2015-01-19 18:06 ` [ARM] Wire up the new scheduler " James Greenhalgh
2015-01-23 15:24 ` James Greenhalgh
2015-01-26 9:14 ` Ramana Radhakrishnan [this message]
2015-01-16 15:16 ` [AArch64] Add a new scheduling " James Greenhalgh
2015-01-16 15:38 ` Ramana Radhakrishnan
2015-01-19 18:09 ` James Greenhalgh
2015-01-19 21:29 ` Gerald Pfeifer
2015-01-19 21:58 ` James Greenhalgh
2015-01-20 8:58 ` Ramana Radhakrishnan
2015-01-20 9:42 ` Marcus Shawcroft
2015-01-20 16:11 ` Gerald Pfeifer
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=CAJA7tRbwBQxqrw6hRW6ifpyAEuTTLY4AyF_2Do3QwRMCCwhuhw@mail.gmail.com \
--to=ramana.gcc@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=ramrad01@arm.com \
--cc=richard.earnshaw@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).