On Wednesday 18 August 2010 19:09:51 ext Thiago Macieira, you wrote:
> On Wednesday 18 August 2010 16:13:01 Arjan van de Ven wrote:
> > On 8/18/2010 6:30 AM, Rémi Denis-Courmont wrote:
> > > The only portable manner to establish NEON support is the __ARM_NEON__
> > > predefined constant, just like __SSE3__ implies SSE3 support.
> > > Obviously, that simply reflects the compiler settings. If you want to
> > > make the decision at run- time, you're going to need operating
> > > system-specific code.
> >
> > it's more complex, at least for __SSE3__
> > you won't get __SSE3__ set unless you tell the compiler you support this
> > instruction, and at that point, the compiler
> > will automatically use the instructions as well.
>
> That's exactly the same as the Neon support.
Yup.
> I wish there was a way to use the intrinsics specifically for a portion of
> the code.
In most recent GCC versions, you can change architecture parameters with a
function granularity using a new function attribute. Those are the examples
from the documentation:
__attribute__((__target__("arch=core2")))
__attribute__((__target__("sse3")))
But I am not sure if/when it will be supported on ARM.
--
Rémi Denis-Courmont
Nokia Devices R&D, Maemo Software, Helsinki
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
