Install script: Altivec check for non Altivec machines

[GoogleCodeExporter]

Added a check if Altivec is available for real when the altivec version is 
loaded.. just to avoid that the Altivec version will crash on not supported 
platform, for example on Sam440

(This check was present in the old afxgroup binary)

Original issue reported on code.google.com by s.hawam...@gmail.com on 21 May 2014 at 11:19

[GoogleCodeExporter]

This might not be possible, because the compiler might add opcodes that are not 
supported, so program might crash even before the altivec check.
What can be done how ever is create a install script that installs the correct 
version for your system.

Original comment by kjetil.h...@gmail.com on 22 May 2014 at 1:42

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Yep seems a good compromise, who know how it was done in the original version ..
Maybe later we can ask this question to afxgroup!

Original comment by s.hawam...@gmail.com on 23 May 2014 at 10:58

[GoogleCodeExporter]

K-L wants to have different config files for different computers.

Original comment by kjetil.h...@gmail.com on 29 May 2014 at 10:32

• Changed title: Install script: Altivec check for non Altivec machines

[GoogleCodeExporter]

I guess that afx didn't compile it with -maltivec, in order to make sure that 
no Altivec opcodes are inserted in the binary, and changed all the ALTIVEC 
defines in normal if statements, and a global variable set by an Altivec 
detection routine. It would have to be seen if the -maltivec compiler switch 
makes any speed improvement.

Original comment by varthal...@gmail.com on 3 Jun 2014 at 11:57