This is the mail archive of the
mailing list for the libc-ports project.
Re: [PATCH] sysdeps/arm/armv7/multiarch/memcpy_impl.S: Improve performance.
- From: OndÅej BÃlka <neleai at seznam dot cz>
- To: "Ryan S. Arnold" <ryan dot arnold at gmail dot com>
- Cc: Carlos O'Donell <carlos at redhat dot com>, Will Newton <will dot newton at linaro dot org>, "libc-ports at sourceware dot org" <libc-ports at sourceware dot org>, Patch Tracking <patches at linaro dot org>, Siddhesh Poyarekar <siddhesh at redhat dot com>
- Date: Sat, 7 Sep 2013 13:54:34 +0200
- Subject: Re: [PATCH] sysdeps/arm/armv7/multiarch/memcpy_impl.S: Improve performance.
- Authentication-results: sourceware.org; auth=none
- References: <520894D5 dot 7060207 at linaro dot org> <CANu=DmiBHoymFKTvaW_VsdhWZEYwkfViz1tTeRgj7H80f0FntA at mail dot gmail dot com> <5220D30B dot 9080306 at redhat dot com> <CANu=DmiXLL9v1Z1KS0sBOs-pL8csEUGc9YE829_-tidKd-GruQ at mail dot gmail dot com> <5220F1F0 dot 80501 at redhat dot com> <CANu=DmhA9QvSe6RS72Db2P=yyjC72fsE8d4QZKHEcNiwqxNMvw at mail dot gmail dot com> <52260BD0 dot 6090805 at redhat dot com> <20130903173710 dot GA2028 at domone dot kolej dot mff dot cuni dot cz> <CAAKybw9Hg69N-U94hcA+7cR0=_xfqSDi8xujQSBr6h0aaEmzHw at mail dot gmail dot com>
On Tue, Sep 03, 2013 at 02:34:54PM -0500, Ryan S. Arnold wrote:
> On Tue, Sep 3, 2013 at 12:37 PM, OndÅej BÃlka <email@example.com> wrote:
> >> I disagree strongly. You *must* come up with a measurable answer and
> >> looking at a graph is never a solution I'm going to accept.
> > You can have that opinion.
> > Looking at performance graphs is most powerful technique how to
> > understand performance. I got most of my improvements from analyzing
> > these.
> Are there any open source pipeline analysis tools? I've found the one
> I've used (proprietary) to be a pretty good indicator of general
> instruction selection optimization/correctness.
After bit of googling I found http://marss86.org/~marss86/index.php/Home
Is anyone familiar with it?
This reminded me to work on project in my backlog. Writing tool that can
legaly shuffle assembler instructions.
Then I run simulated annaling to get optimal sheduling for given processor
With dryrun data this will be close to real performance on small size so
I could get some percents there.