I don't read ARM assembly so I'll pass this by someone who might. Otherwise, I'll ...
14 years, 5 months ago
(2010-06-03 21:32:07 UTC)
#4
I don't read ARM assembly so I'll pass this by someone who might. Otherwise,
I'll trust that it works and thus I think it's good to go.
You've signed either the individual or corporate copyright agreement, right?
On 2010/06/03 21:32:07, agl wrote: > I don't read ARM assembly so I'll pass this ...
14 years, 5 months ago
(2010-06-03 22:51:49 UTC)
#5
On 2010/06/03 21:32:07, agl wrote:
> I don't read ARM assembly so I'll pass this by someone who might. Otherwise,
> I'll trust that it works and thus I think it's good to go.
>
> You've signed either the individual or corporate copyright agreement, right?
Corporate copyright agreement. Thanks for passing that code on.
On 2010/06/04 14:48:09, agl wrote: > landed as Skia r573 Hmmm. Looking at the memset32 ...
14 years, 3 months ago
(2010-07-21 14:30:33 UTC)
#7
On 2010/06/04 14:48:09, agl wrote:
> landed as Skia r573
Hmmm. Looking at the memset32 code here, it's running slower for me on a
Versatile Express board than the normal portable code. pgalizia: what hardware
did you test on please?
I've also found some some normal optimised ARM code (non-neon) which runs a LOT
faster for me. See
http://www.netmite.com/android/mydroid/1.6/system/core/libcutils/memset32.S
for the code. Might be worth pulling into upstream skia?
On Wed, Jul 21, 2010 at 10:30 AM, <EinvalSledge@googlemail.com> wrote: > Hmmm. Looking at the ...
14 years, 3 months ago
(2010-07-21 15:43:58 UTC)
#8
On Wed, Jul 21, 2010 at 10:30 AM, <EinvalSledge@googlemail.com> wrote:
> Hmmm. Looking at the memset32 code here, it's running slower for me on a
> Versatile Express board than the normal portable code. pgalizia: what
> hardware did you test on please?
>
> I've also found some some normal optimised ARM code (non-neon) which
> runs a LOT faster for me. See
>
> http://www.netmite.com/android/mydroid/1.6/system/core/libcutils/memset32.S
>
> for the code. Might be worth pulling into upstream skia?
I pretty much have to depend on others to tell me what the best code
for ARM is. I don't have an ARM build nor ARM hardware.
You're also welcome to submit patches.
AGL
I suggest we submit both version to the tree: neon and non-neon-ARM, in separate files. ...
14 years, 3 months ago
(2010-07-22 12:18:23 UTC)
#9
I suggest we submit both version to the tree: neon and non-neon-ARM,
in separate files. That way a given platform can just modify their
Makefile to pull in which ever one is deemed fastest for them.
On Wed, Jul 21, 2010 at 11:43 AM, Adam Langley <agl@chromium.org> wrote:
> On Wed, Jul 21, 2010 at 10:30 AM, <EinvalSledge@googlemail.com> wrote:
>> Hmmm. Looking at the memset32 code here, it's running slower for me on a
>> Versatile Express board than the normal portable code. pgalizia: what
>> hardware did you test on please?
>>
>> I've also found some some normal optimised ARM code (non-neon) which
>> runs a LOT faster for me. See
>>
>> http://www.netmite.com/android/mydroid/1.6/system/core/libcutils/memset32.S
>>
>> for the code. Might be worth pulling into upstream skia?
>
> I pretty much have to depend on others to tell me what the best code
> for ARM is. I don't have an ARM build nor ARM hardware.
>
> You're also welcome to submit patches.
>
>
> AGL
>
That works, considering that different ARM systems may have different optimal configurations. We were testing ...
14 years, 3 months ago
(2010-07-22 14:17:31 UTC)
#10
That works, considering that different ARM systems may have different
optimal configurations.
We were testing against Qualcomm Snapdragon 8650 for that particular update.
It'll be interesting to see how that other version works on that platform as
well.
Thanks,
Pat
> -----Original Message-----
> From: Mike Reed [mailto:reed@android.com]
> Sent: Thursday, July 22, 2010 8:18 AM
> To: Adam Langley
> Cc: pgalizia@codeaurora.org; EinvalSledge@googlemail.com;
> reply@codereview.appspotmail.com
> Subject: Re: Add Neon-based memset32/16 for ARM (issue1157045)
>
> I suggest we submit both version to the tree: neon and non-neon-ARM,
> in separate files. That way a given platform can just modify their
> Makefile to pull in which ever one is deemed fastest for them.
>
> On Wed, Jul 21, 2010 at 11:43 AM, Adam Langley <agl@chromium.org>
> wrote:
> > On Wed, Jul 21, 2010 at 10:30 AM, <EinvalSledge@googlemail.com>
> wrote:
> >> Hmmm. Looking at the memset32 code here, it's running slower for me
> on a
> >> Versatile Express board than the normal portable code. pgalizia:
> what
> >> hardware did you test on please?
> >>
> >> I've also found some some normal optimised ARM code (non-neon) which
> >> runs a LOT faster for me. See
> >>
> >>
> http://www.netmite.com/android/mydroid/1.6/system/core/libcutils/memset
> 32.S
> >>
> >> for the code. Might be worth pulling into upstream skia?
> >
> > I pretty much have to depend on others to tell me what the best code
> > for ARM is. I don't have an ARM build nor ARM hardware.
> >
> > You're also welcome to submit patches.
> >
> >
> > AGL
> >
Issue 1157045: Add Neon-based memset32/16 for ARM
Created 14 years, 6 months ago by pgalizia
Modified 14 years, 2 months ago
Reviewers: agl, reed, Sledge
Base URL: http://skia.googlecode.com/svn/trunk/src
Comments: 0