t
Subject: [png-mng-implement] Use of memcpy() in libpng [Fwd from
linaro-toolchain list]
Re: Use of memcpy() in libpng
David Gilbert
Tue, 27 Sep 2011 06:20:14 -0700
On 27 September 2011 14:16, Christian Robottom Reis wrote:
> On Tue, Sep 27, 2011 at 09:47:33AM +0100, Ramana Radhakrishn
> If you guys could take a look at this there is a potential requirement
> for the MMWG around libpng optimization; we could fit this in along with
> other work (possible vectorizing, etc) on that component.
Getting better block operations out of the compiler is something we
are interested in and
On 27 September 2011 14:16, Christian Robottom Reis wrote:
> On Tue, Sep 27, 2011 at 09:47:33AM +0100, Ramana Radhakrishnan wrote:
>> On 26 September 2011 21:51, Michael Hope wrote:
>> > Saw this on the linaro-multimedia list:
>> > http://lists.linaro.org/pipermail/linaro-multimedia/2011-Septemb
On Tue, Sep 27, 2011 at 09:47:33AM +0100, Ramana Radhakrishnan wrote:
> On 26 September 2011 21:51, Michael Hope wrote:
> > Saw this on the linaro-multimedia list:
> > http://lists.linaro.org/pipermail/linaro-multimedia/2011-September/74.html
> >
> > libpng spends a significant amount of time
On 26 September 2011 21:51, Michael Hope wrote:
> Saw this on the linaro-multimedia list:
> http://lists.linaro.org/pipermail/linaro-multimedia/2011-September/74.html
>
> libpng spends a significant amount of time in memcpy(). This might
> tie in with Ramana's investigation or the unaligned
Saw this on the linaro-multimedia list:
http://lists.linaro.org/pipermail/linaro-multimedia/2011-September/74.html
libpng spends a significant amount of time in memcpy(). This might
tie in with Ramana's investigation or the unaligned access work by
allowing more memcpy()s to be inlined.
--
