Re: hot spot on the vsub.f32 instruction

2013-05-17 Thread Renato Golin
On 17 May 2013 14:45, Mans Rullgard wrote: > I suppose those who have a need for this information already know > how to interpret those values. Translating the ARM IDs to model > names would be rather trivial. > Great! Do I hear someone volunteering to implement that in the Kernel? ;) cheers,

Re: hot spot on the vsub.f32 instruction

2013-05-17 Thread Mans Rullgard
On 17 May 2013 14:26, Peter Maydell wrote: > On 17 May 2013 14:03, Mans Rullgard wrote: >> On 17 May 2013 13:30, Renato Golin wrote: >>> Why don't we print full information like Intel? >> >> The part you snipped: >> CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x

Re: hot spot on the vsub.f32 instruction

2013-05-17 Thread Peter Maydell
On 17 May 2013 14:03, Mans Rullgard wrote: > On 17 May 2013 13:30, Renato Golin wrote: >> Why don't we print full information like Intel? > > The part you snipped: > >>> CPU implementer : 0x41 >>> CPU architecture: 7 >>> CPU variant : 0x0 >>> CPU part : 0xc05 >>> CPU revision : 1 > > Th

Re: hot spot on the vsub.f32 instruction

2013-05-17 Thread Mans Rullgard
On 17 May 2013 13:30, Renato Golin wrote: > On 17 May 2013 08:18, YongQin Liu wrote: >> > * What platform are you testing on? >> The device I am testing on is an SP8810 device. here is the content of the >> cpuinfo > > I believe that's a Cortex-A5. > >> root@android:/ # cat /proc/cpuinfo >> Proce

Re: hot spot on the vsub.f32 instruction

2013-05-17 Thread Renato Golin
On 17 May 2013 08:18, YongQin Liu wrote: > I Compiled it with the android-ndk-r8d with the attached build_native.sh > script. > That's a gcc 4.7 right? > * What platform are you testing on? > The device I am testing on is an SP8810 device. here is the content of the > cpuinfo > I believe that

Re: hot spot on the vsub.f32 instruction

2013-05-14 Thread Renato Golin
On 14 May 2013 13:23, Will Newton wrote: > It looks like there is a data dependency on the preceding load, it > might be worth looking into prefetching the data, either manually or > maybe try -fprefetch-loop-arrays? > I agree with Matt on needing more info, but I also agree with Will that a pre

Re: hot spot on the vsub.f32 instruction

2013-05-14 Thread Matthew Gretton-Dann
YongQin, On 13/05/13 13:52, YongQin Liu wrote: Hi, All The attachment file is analysed by the streamline tool. How to do you think about the vsub.f32 hot spot there? Is there any way we can improve that? Maybe - but you give very little information for us to help you. We need more context -

Re: hot spot on the vsub.f32 instruction

2013-05-14 Thread Will Newton
On 13 May 2013 13:52, YongQin Liu wrote: > Hi, All > > The attachment file is analysed by the streamline tool. > How to do you think about the vsub.f32 hot spot there? > Is there any way we can improve that? It looks like there is a data dependency on the preceding load, it might be worth looking