On Thursday 19 August 2010 14:11:19 Alexander Sack wrote: > On Wed, Aug 18, 2010 at 06:09:37AM -0700, Arjan van de Ven wrote: > > couldn't QT read /proc/cpuinfo (or do the equivalent of cpuid) > > instead of looking for the env variable? > > what others are doing is catching the sigill that happens if neon code > is not supported and then runtime falling back to non-neon code paths. > > Hope thats an option as thats easiest for distributions.
That requires a fork. I don't think that resuming an application after a
caught SIGILL is a good idea. (At least on ARM the instruction size is fixed,
on other platforms it isn't)
I've seen libvlc do that. It was the source of a very, very weird problem
further down in D-Bus.
(They exited the process with exit(3) instead of _exit(2))
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
