* Sam Hocevar [EMAIL PROTECTED] [2007-01-29 02:52]:
The way I understand the -maltivec flag is make the compiler aware
of AltiVec instructions and the vector type, but only generate AltiVec
code if the altivec.h intrinsics are being used, whereas -mabi=altivec
means generate AltiVec code
On Thu, Apr 19, 2007, Martin Michlmayr wrote:
01:06 tbm any comment on
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408918
01:06 apinski yes it is not a bug
01:08 tbm why?
01:08 apinski because -maltivec enables altivec usage in general
01:09 apinski Generate code that uses (does not
* Sam Hocevar [EMAIL PROTECTED] [2007-04-20 02:52]:
Do you know how the GCC developers would suggest handling vector
types in a C structure or C++ object that are only used by functions
called if AltiVec support was detected at runtime? Because you currently
cannot do that without
On 4/19/07, Martin Michlmayr [EMAIL PROTECTED] wrote:
* Sam Hocevar [EMAIL PROTECTED] [2007-04-20 02:52]:
Do you know how the GCC developers would suggest handling vector
types in a C structure or C++ object that are only used by functions
called if AltiVec support was detected at runtime?
Package: gcc-4.1
Version: 4.1.1-21
Severity: important
The way I understand the -maltivec flag is make the compiler aware
of AltiVec instructions and the vector type, but only generate AltiVec
code if the altivec.h intrinsics are being used, whereas -mabi=altivec
means generate AltiVec code
5 matches
Mail list logo
