Bug#686231: dragonegg-4.6: internal compiler error: Segmentation fault with llvm-gcc

2012-09-04 Thread Vincent Lefevre
retitle 686231 dragonegg-4.6 built incorrectly - internal compiler error: Segmentation fault with llvm-gcc / cpp-4.6 4.6.3-9 severity 686231 serious thanks Raising severity because llvm-gcc is unusable and its build is incorrect (was it built in an incorrect environment or is there any missing bu

Bug#686231: dragonegg-4.6: internal compiler error: Segmentation fault with llvm-gcc

2012-08-30 Thread Vincent Lefevre
reassign 686231 cpp-4.6 found 686231 4.6.3-9 thanks On 2012-08-30 13:08:28 +0200, Vincent Lefevre wrote: > Package: dragonegg-4.6 > Version: 3.1-2 > Severity: important > > I get the following ICE on the following program: > > int f (unsigned int u) > { > unsigned int c; > __asm__ ("bsr %1,%

Bug#686231: dragonegg-4.6: internal compiler error: Segmentation fault with llvm-gcc

2012-08-30 Thread Vincent Lefevre
With "valgrind --trace-children=yes llvm-gcc -c test.i", I get: [...] ==27077== Memcheck, a memory error detector ==27077== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==27077== Using Valgrind-3.8.0 and LibVEX; rerun with -h for copyright info ==27077== Command: /usr/lib/gcc/x8

Bug#686231: dragonegg-4.6: internal compiler error: Segmentation fault with llvm-gcc

2012-08-30 Thread Vincent Lefevre
Package: dragonegg-4.6 Version: 3.1-2 Severity: important I get the following ICE on the following program: int f (unsigned int u) { unsigned int c; __asm__ ("bsr %1,%0" : "=r" (c) : "rm" (u)); return 0; } $ llvm-gcc -c test.i *** WARNING *** there are active plugins, do not report this as