Re: Memcpy and memset

2011-09-05 Thread Michael Hope
On Fri, Sep 2, 2011 at 4:51 AM, David Gilbert wrote: > Hi Michael, >  I've just committed a pair of memcpy's into src/linaro-a9 - memcpy.S > that is armv7 > and memcpy-hybrid.S that is a Neon hybrid which uses neon for non-aligned > cases > and for large (128K or larger) copies.   I've also (acci

Agenda - performance call - 2011-09-06

2011-09-05 Thread Ramana Radhakrishnan
Hi, I've put a draft agenda for tomorrow's call at https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-09-06 Is there something else folks would like to add to this ? Follow-up on the cortex-strings discussion from today's call ? cheers Ramana

Re: Benchmarking / justifying cortex-strings

2011-09-05 Thread David Gilbert
On 5 September 2011 17:40, Christian Robottom Reis wrote: > On Mon, Sep 05, 2011 at 03:21:49PM +1200, Michael Hope wrote: >> memchr is good.  memset could be better for blocks of less than 1k. >> strchr gets second place but is eclipsed by newlib's version.  strcmp >> need work.  strcmp is good. >

Re: Benchmarking / justifying cortex-strings

2011-09-05 Thread Christian Robottom Reis
On Mon, Sep 05, 2011 at 03:21:49PM +1200, Michael Hope wrote: > memchr is good. memset could be better for blocks of less than 1k. > strchr gets second place but is eclipsed by newlib's version. strcmp > need work. strcmp is good. It's strcpy which is good in this last sentence, though it basic

Re: Benchmarking / justifying cortex-strings

2011-09-05 Thread David Gilbert
On 5 September 2011 04:21, Michael Hope wrote: > On Fri, Sep 2, 2011 at 4:08 PM, Michael Hope wrote: >> Hi Dave.  I've been hacking away and have checked in a couple of >> benchmarking and plotting scripts to lp:cortex-strings.  The current >> results are at: >>  http://people.linaro.org/~michael

[ACTIVITY] 29th - August - 3rd September

2011-09-05 Thread Andrew Stubbs
* Linaro GCC Fixed up, committed and posted two bug fixes to my thumb2 constants patches, found by other people running FSF trunk. Analysed bug lp:836401 / pr50193, developed a fix, and posted it both upstream and to launchpad for testing. The launchpad tests have come back clean, and the pa