search for: spfp

...the cost table is being built over the last months. The only way to get this result is indirectly via the cost model but the > backend must still support vectorized IR (it is part of the language) via > scalarization. > Absolutely! There are two problems to solve: increase the cost for SPFP when UseNEONForSinglePrecisionFP is false, so that vectorizers don't generate such code, and legalize correctly in the backend, for vector code that does not respect that flag. (You can of course assign UMAX cost for all floating point vector types in > the cost model for ARM and get the d...

...ll have to solve the real problem in the ARM backend. > The only way to get this result is indirectly via the cost model but the backend must still support vectorized IR (it is part of the language) via scalarization. > > Absolutely! There are two problems to solve: increase the cost for SPFP when UseNEONForSinglePrecisionFP is false, so that vectorizers don't generate such code, and legalize correctly in the backend, for vector code that does not respect that flag. > > > (You can of course assign UMAX cost for all floating point vector types in the cost model for ARM and...

On Jun 7, 2013, at 9:22 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 7 June 2013 14:49, Arnold Schwaighofer <aschwaighofer at apple.com> wrote: > It is not the vectorizer that is the issue, it is the ARM backend that currently translates vectorized floating point IR to NEON instructions (it should scalarize it if desired to do so - i.e. if people care about

On 7 June 2013 14:49, Arnold Schwaighofer <aschwaighofer at apple.com> wrote: > It is not the vectorizer that is the issue, it is the ARM backend that > currently translates vectorized floating point IR to NEON instructions (it > should scalarize it if desired to do so - i.e. if people care about > denormals). > Hi Arnold, Can't the vectorizer not generate the v4f32