[Development] QTBUG-30440: restricting the SIMD files

Thiago Macieira thiago.macieira at intel.com
Tue Aug 20 16:38:27 CEST 2013


On ter├ža-feira, 20 de agosto de 2013 07:23:28, Knoll Lars wrote:
> Here's another idea (no idea if we could make it work though): If the
> methods don't expose any of the Qt types as API, we could try putting all
> the #include's that we use in the implementation into an anonymous
> namespace.

That might work. I'll keep investigating.

Meanwhile, for all ARM builds, if your code is meant to run on systems without 
Neon, consider adding -no-neon to the configure command-line. We haven't heard 
any reports of SSE2 or AVX leakage.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130820/e8205849/attachment.sig>


More information about the Development mailing list