From: Evandro Menezes <e.menezes@samsung.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Andrew Pinski <pinskia@gmail.com>,
"philipp.tomsich@theobroma-systems.com"
<philipp.tomsich@theobroma-systems.com>,
Benedikt Huber <benedikt.huber@theobroma-systems.com>,
nd@arm.com
Subject: Re: [AArch64] Emit square root using the Newton series
Date: Wed, 27 Apr 2016 15:45:00 -0000 [thread overview]
Message-ID: <5720DE79.2030006@samsung.com> (raw)
In-Reply-To: <20160427142351.GC40892@arm.com>
On 04/27/16 09:23, James Greenhalgh wrote:
> On Tue, Apr 12, 2016 at 01:14:51PM -0500, Evandro Menezes wrote:
>> On 04/05/16 17:30, Evandro Menezes wrote:
>>> On 04/05/16 13:37, Wilco Dijkstra wrote:
>>>> I can't get any of these to work... Not only do I get a large
>>>> number of collisions and duplicated
>>>> code between these patches, when I try to resolve them, all I
>>>> get is crashes whenever I try
>>>> to use sqrt (even rsqrt stopped working). Do you have a patchset
>>>> that applies cleanly so I can
>>>> try all approximation routines?
>>> The original patches should be independent of each other, so
>>> indeed they duplicate code.
>>>
>>> This patch suite should be suitable for testing.
> Take look at other patch sets posted to this list for examples of how
> to make review easier.
>
> Please send a series of emails tagged:
>
> [Patch 0/3 AArch64] Add infrastructure for more approximate FP operations
> [PATCH 1/3 AArch64] Add more choices for the reciprocal square root approximation
> [PATCH 2/3 AArch64] Emit square root using the Newton series
> [PATCH 3/3 AArch64] Emit division using the Newton series
>
> One patch per email, with the dependencies explicit like this, is
> infinitely easier to follow than the current structure of your patch set.
>
> I'm not trying to be pedantic for the sake of it, I'm genuinely unsure where
> the latest patch versions currently are and how I should apply them to a
> clean tree for review.
I can certainly create such a series, but the patch above should be
suitable for testing.
Thank you,
--
Evandro Menezes
next prev parent reply other threads:[~2016-04-27 15:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 22:50 Evandro Menezes
2016-03-24 20:30 ` [AArch64] " Evandro Menezes
2016-04-01 22:45 ` Evandro Menezes
2016-04-04 16:32 ` Evandro Menezes
[not found] ` <DB3PR08MB008902F0F0AFA3B1F1C91511839E0@DB3PR08MB0089.eurprd08.prod.outlook.com>
2016-04-05 22:30 ` Evandro Menezes
2016-04-12 18:15 ` Evandro Menezes
2016-04-21 18:44 ` Evandro Menezes
2016-04-27 14:24 ` James Greenhalgh
2016-04-27 15:45 ` Evandro Menezes [this message]
[not found] <AM3PR08MB00886499882773F3C8B9F71D83B30@AM3PR08MB0088.eurprd08.prod.outlook.com>
[not found] ` <011d01d17a26$31b3ade0$951b09a0$@samsung.com>
2016-03-10 16:52 ` Wilco Dijkstra
2016-03-10 16:58 ` Evandro Menezes
2016-03-10 19:10 ` Wilco Dijkstra
2016-03-10 22:15 ` Evandro Menezes
2016-03-11 1:06 ` Wilco Dijkstra
2016-03-14 16:39 ` Evandro Menezes
2016-03-14 19:13 ` Wilco Dijkstra
2016-03-16 21:44 ` Evandro Menezes
-- strict thread matches above, loose matches on Subject: below --
2015-12-08 21:35 Evandro Menezes
2015-12-09 14:05 ` Marcus Shawcroft
2015-12-09 16:31 ` Evandro Menezes
2015-12-09 16:52 ` Kyrill Tkachov
2015-12-09 16:59 ` Evandro Menezes
2015-12-09 17:03 ` Kyrill Tkachov
2015-12-09 17:16 ` Kyrill Tkachov
2015-12-09 18:50 ` Evandro Menezes
2015-12-10 10:30 ` Kyrill Tkachov
2016-02-23 0:50 ` Evandro Menezes
2016-02-26 15:00 ` James Greenhalgh
2016-02-26 23:42 ` Evandro Menezes
2016-02-26 23:46 ` Evandro Menezes
2016-02-16 20:56 ` Evandro Menezes
2016-03-04 0:22 ` Evandro Menezes
2016-03-08 22:08 ` Evandro Menezes
2016-03-08 22:18 ` Evandro Menezes
2016-03-08 22:20 ` Evandro Menezes
2016-03-16 19:45 ` Evandro Menezes
2016-03-17 14:55 ` James Greenhalgh
2016-03-17 16:25 ` Evandro Menezes
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=5720DE79.2030006@samsung.com \
--to=e.menezes@samsung.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=benedikt.huber@theobroma-systems.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=nd@arm.com \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=pinskia@gmail.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).