From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Richard Earnshaw <Richard.Earnshaw@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>, James Greenhalgh <James.Greenhalgh@arm.com>
Subject: Re: [PATCH][AArch64] Change FP reassociation width
Date: Tue, 13 Jun 2017 09:43:00 -0000 [thread overview]
Message-ID: <VI1PR0802MB2621961314F20CEDB36A3C9783C20@VI1PR0802MB2621.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <acd5c386-03e7-9fa6-5c2e-9fc89e5f1a74@arm.com>
Richard Earnshaw (lists) wrote:
>
> Why 1 and not 2? Many processors have 2 fp pipes and forcing this down
> to a sequential stream is not obviously the right thing.
1 was faster than 2. Like I said, the reassociation is too aggressive and even
splits multiply-add rather than keeping them. Until reassociation is fixed and
able to split a complex expression into 2 independent chains of similar depth
while keeping multiply-accumulate operations, it is best to set it to 1 for now.
> If reassociation is is causing excess spilling, then the right fix for
> that is to look at the pressure model, not hammer the problem away.
The problem of the GCC scheduler hugely increasing register pressure has
existed for many years with no progress being made. Unless we're willing to
start a project improving this I do not believe there will be a solution any time
soon. So changing the association width is the best solution for the time being.
Wilco
next prev parent reply other threads:[~2017-06-13 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 10:50 Wilco Dijkstra
2017-06-13 9:07 ` Richard Earnshaw (lists)
2017-06-13 9:43 ` Wilco Dijkstra [this message]
2017-06-14 14:30 ` James Greenhalgh
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=VI1PR0802MB2621961314F20CEDB36A3C9783C20@VI1PR0802MB2621.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@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).