Suggested buildd log check

Hi, You wrote[1]: > If you have ideas for warnings/diagnostics visibile in buildd logs > that are worth having listed in a view like that, please let me > know. I'm not sure how your infrastructure copes with something like this, but I would find it useful to have gcc 4.6's machine-parsable warn

Processed: Raising severity to 'serious'

Processing commands for cont...@bugs.debian.org: > severity 635126 serious Bug #635126 [gcc-4.6] gcc-4.6: miscompilation with -ftree-sra Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 635126: http://bugs.debian.org/cgi-

Bug#635126: Raising severity to 'serious'

severity 635126 serious thanks With my sparc port maintainer hat on, I'm setting severity of this bug back to serious. --ftree-sre is on by default for -O2, so pretty much every sparc binary in the archive is potentially affected by it. The fact that the test code does not do anything exotic to

Bug#635126: Standalone test case

Hi, Attached is a standalone test case for this bug, obtained on an up-to-date sid/sparc system. With it I see the following behavior: jurij@debian:~$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/sparc-linux-gnu/4.6/lto-wrapper Target: sparc-linux-gnu Configured

Results for 4.4.6 (Debian/Linaro 4.4.6-11) testsuite on arm-unknown-linux-gnueabihf

LAST_UPDATED: Fri Sep 16 15:20:39 UTC 2011 (revision 178907) Native configuration is arm-unknown-linux-gnueabihf === libgomp tests === Running target unix FAIL: libgomp.c/lock-1.c execution test WARNING: program timed out. FAIL: libgomp.c/lock-3.c execution test