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 ru
* 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 "con
On Thu, Apr 19, 2007, Martin Michlmayr wrote:
> 01:06 any comment on
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408918
> 01:06 yes it is not a bug
> 01:08 why?
> 01:08 because -maltivec enables altivec usage in general
> 01:09 "Generate code that uses (does not use) AltiVec
> inst
* 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 intrinsics are being used", whereas -mabi=altivec
> means "generate AltiVec code whe
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 intrinsics are being used", whereas -mabi=altivec
means "generate AltiVec code wherever
5 matches
Mail list logo
