Bug#528741: -floop-block causes numerous ICEs
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++)
*dest++ = 0;
return 0;
}
% gcc-4.4 -O1 -floop-block foo.c -o foo
foo.c: In function ‘main’:
foo.c:2: internal compiler error: in expand_scalar_variables_expr, at
graphite.c:4295
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
%
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gcc-4.4 depends on:
ii binutils 2.19.1-1 The GNU assembler, linker and bina
ii cpp-4.4 4.4.0-4The GNU C preprocessor
ii gcc-4.4-base 4.4.0-4The GNU Compiler Collection (base
ii libc6 2.9-12 GNU C Library: Shared libraries
ii libgcc1 1:4.4.0-4 GCC support library
ii libgomp1 4.4.0-4GCC OpenMP (GOMP) support library
Versions of packages gcc-4.4 recommends:
ii libc6-dev 2.9-12 GNU C Library: Development Librari
Versions of packages gcc-4.4 suggests:
pn gcc-4.4-doc(no description available)
pn gcc-4.4-locales(no description available)
pn gcc-4.4-multilib (no description available)
pn libgcc1-dbg(no description available)
pn libgomp1-dbg (no description available)
pn libmudflap0-4.4-dev(no description available)
pn libmudflap0-dbg(no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637885: g++ -m32 does not work out of the box
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. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages g++-4.6 depends on: ii gcc-4.6 4.6.1-6 GNU C compiler ii gcc-4.6-base4.6.1-6 GCC, the GNU Compiler Collection ( ii libc6 2.13-16 Embedded GNU C Library: Shared lib ii libcloog-ppl0 0.15.9-3 the Chunky Loop Generator (runtime ii libgmp102:5.0.1+dfsg-7 Multiprecision arithmetic library ii libgmpxx4ldbl 2:5.0.1+dfsg-7 Multiprecision arithmetic library ii libmpc2 0.9-3multiple precision complex floatin ii libmpfr43.0.1-5 multiple precision floating-point ii libppl-c4 0.11.2-4 Parma Polyhedra Library (C interfa ii libppl9 0.11.2-4 Parma Polyhedra Library (runtime l ii libstdc++6-4.6-dev 4.6.1-6 GNU Standard C++ Library v3 (devel ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime g++-4.6 recommends no packages. Versions of packages g++-4.6 suggests: ii g++-4.6-multilib 4.6.1-6GNU C++ compiler (multilib files) pn gcc-4.6-doc(no description available) pn libstdc++6-4.6-dbg (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110815141917.12590.923.reportbug@w00t
Bug#637885: g++ -m32 does not work out of the box
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 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. > > there was a bug report asking for the current behaviour. If you want multilib, > please install it. Well this is a bug report asking for the previous, non-broken behaviour. I found no such bug report in gcc-4.4, gcc-4.5 or gcc-4.6. Could you please point it to me? I could not find anything in any of the package changelogs either. I hope you understand that I don't understand the rationale for deliberately breaking the -m32 flag upon upgrade or for believing this is not a "normal" bug, so I'm interested in knowing the other reporter's arguments. Cheers, -- Sam. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110818130241.gb23...@hocevar.net
Bug#408918: [powerpc] -maltivec generates AltiVec code when not asked to
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 possible".
However, the following code, which doesn't even include ,
generates AltiVec code with gcc-4.0 and gcc-4.1:
/* gcc -O3 -maltivec -c foo.c -S -o - */
#include
extern func(void **, void**, void *);
void test(void) {
struct foo { int a[4]; } var0;
void *var1, *var2;
memset(&var0, 0, sizeof(var0));
func(&var1, &var2, &var0);
}
Here is the output:
.file "foo.c"
.section".text"
.align 2
.p2align 4,,15
.globl test
.type test, @function
test:
mflr 0
stwu 1,-48(1)
vxor 0,0,0
addi 5,1,16
stw 0,52(1)
addi 3,1,8
addi 4,1,12
stvx 0,0,5
bl func
lwz 0,52(1)
addi 1,1,48
mtlr 0
blr
.size test,.-test
.ident "GCC: (GNU) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)"
.section.note.GNU-stack,"",@progbits
"vxor" is an AltiVec instruction. I don't think it should be there, and
it breaks software that make the same assumption (ffmpeg, for instance).
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-powerpc
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages gcc-4.1 depends on:
ii binutils2.17-3 The GNU assembler, linker and bina
ii cpp-4.1 4.1.1-21 The GNU C preprocessor
ii gcc-4.1-base4.1.1-21 The GNU Compiler Collection (base
ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries
ii libgcc1 1:4.1.1-21 GCC support library
ii libssp0 4.1.1-21 GCC stack smashing protection libr
Versions of packages gcc-4.1 recommends:
ii libc6-dev 2.3.6.ds1-10 GNU C Library: Development Librari
pn libmudflap0-dev(no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#408918: [powerpc] -maltivec generates AltiVec code when not asked to
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 > instructions, and also enable the use of built-in functions that > allow more direct access to the AltiVec instruction set. You may > also need to set -mabi=altivec to adjust the current ABI with AltiVec > ABI enhancements." [that's from the docs] Thanks, I can certainly live with this not being a bug as long as it's well known. 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 "contaminating" each and every object using these types with AltiVec instructions all over the place. Regards, -- Sam. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
