Hi Ramana,
as you pointed out, in the gcc.dg/vect/vect-double-reduc-6.c test case,
using compiler options as described in PR 51819, we see the following
inefficient code generation:
vmov.32 r2, d28[0] @ 57vec_extractv4si [length = 4]
vmov.32 r1, d22[0] @ 84vec_
On Tue, Jan 31, 2012 at 02:22:27PM +1300, Michael Hope wrote:
> One of our cards this quarter was -O3 as a performance theme which
> included doing a write up on the advantages and usability of -O3.
> This write up is at:
> https://wiki.linaro.org/Internal/ToolChain/BuildingAtO3
>
> A sanitised v
On Tue, Jan 31, 2012 at 2:22 PM, Michael Hope wrote:
> A sanitised version with non-sharable benchmark data is at:
> https://wiki.linaro.org/Internal/ToolChain/BuildingAtO3
Which, of course, should read:
https://wiki.linaro.org/MichaelHope/Sandbox/BuildingAtO3
-- Michael
_
On Wed, Feb 1, 2012 at 7:09 AM, Christian Robottom Reis wrote:
> On Tue, Jan 31, 2012 at 02:22:27PM +1300, Michael Hope wrote:
>> One of our cards this quarter was -O3 as a performance theme which
>> included doing a write up on the advantages and usability of -O3.
>> This write up is at:
>> http
On Wed, Feb 1, 2012 at 2:51 PM, Michael Hope wrote:
> On Wed, Feb 1, 2012 at 7:09 AM, Christian Robottom Reis
> wrote:
>> On Tue, Jan 31, 2012 at 02:22:27PM +1300, Michael Hope wrote:
>>> One of our cards this quarter was -O3 as a performance theme which
>>> included doing a write up on the adva
