illegal instruction - create compile variants ?

[David Timms]

On 02/05/11 06:31, Kevin Kofler wrote:
> David Timms wrote:
>> Should I be suggesting to upstream to attempt to detect CPU before
>> running non-available instructions, eg as part of app startup ?
Further, what can I run over an existing executable to detect what CPU 
it was built for, ie what instuctions have been included ?

> Yes, all the packages which have WORKING support for SSE etc. in Fedora do
> that. See e.g.
> https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/entry/solid/solid/backends/shared/cpufeatures.cpp
> https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/entry/solid/solid/backends/udev/cpuinfo.cpp
> https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/entry/solid/solid/backends/udev/udevprocessor.cpp
> for the implementation Solid (in kdelibs) uses.
Thanks Kevin, I'll make the suggestion to developers, and see if they 
are interested. Cheers, David.