On Mon, Aug 15, 2011, Matthias Klose wrote:
> tag 637885 + wontfix
> severity 637885 wishlist
> thanks
>
> On 08/15/2011 04:19 PM, Sam Hocevar wrote:
> >g++ -m32 does not work out of the box because g++-4.6 only suggests
> > g++-4.6-multilib instead of at least r
Package: g++-4.6
Version: 4.6.1-6
Severity: normal
g++ -m32 does not work out of the box because g++-4.6 only suggests
g++-4.6-multilib instead of at least recommending it. It would be nice
if the dependency was pulled by default.
The same goes for gcc-4.6 / gcc-4.6-multilib, by the way.
-
Package: gcc-4.4
Version: 4.4.0-4
Severity: normal
gcc-4.4's new -flopp-block flag does not seem to work properly. Here
is a simple test case:
int buffer[256*256];
int main(void)
{
int *dest = buffer;
int x, y;
for(x = 0; x < 256; x++)
for(y = 0; y < 256; y++)
*
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
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
