From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: "siddhesh@sourceware.org" <siddhesh@sourceware.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: [PING][PATCH v3] Disable reg offset in quad-word store for Falkor
Date: Mon, 19 Feb 2018 12:58:00 -0000 [thread overview]
Message-ID: <DB6PR0801MB20534A330EF88ED5F34992A983C80@DB6PR0801MB2053.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <92252605-6083-ea7c-1026-2c1024839fe8@sourceware.org>
Siddhesh Poyarekar wrote:
> On Thursday 15 February 2018 07:50 PM, Wilco Dijkstra wrote:
>> So it seems to me using existing cost mechanisms is always preferable, even if you
>> currently can't differentiate between loads and stores.
>
> Luis is working on address cost adjustments among other things, so I
> guess the path of least resistance for gcc8 is to have those adjustments
> go in and then figure out how much improvement this patch (or separating
> loads and stores) would get on top of that. Would that be acceptable?
Yes adjusting costs is not an issue as that's clearly something we need to improve
anyway. Having numbers for both approaches would be useful, however I think it's still
best to go with the cost approach for GCC8 as that should get most of the gain.
Wilco
next prev parent reply other threads:[~2018-02-19 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 14:20 Wilco Dijkstra
2018-02-16 4:42 ` Siddhesh Poyarekar
2018-02-19 12:58 ` Wilco Dijkstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-09 7:33 [PATCH " Siddhesh Poyarekar
2018-02-15 9:52 ` [PING][PATCH " Siddhesh Poyarekar
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=DB6PR0801MB20534A330EF88ED5F34992A983C80@DB6PR0801MB2053.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--cc=siddhesh@sourceware.org \
/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).