On 29 June 2012 23:07, Ulrich Weigand Ulrich.Weigand@de.ibm.com wrote:
linaro-toolchain-bounces@lists.linaro.org wrote on 29.06.2012 12:19:52:
For Uli's merge request, there is only one new UNSUPPORTED:
-PASS: gcc.dg/simulate-thread/atomic-other-int.c -O0 -g thread simulation
test
+UNSUPPORTED: gcc.dg/simulate-thread/atomic-other-int.c -O0 -g thread simulation test
Log at: http://ex.seabright.co.nz/build/gcc-linaro-4.7 +bzr115000~uweigand~lp-1010826-4.7-p2/logs/armv7l-precise-cbuild339- ursa4-cortexa9hfr1/ (This test is respawned by Michael)
But the case PASS in the original test. Log at: http://ex.seabright.co.nz/build/gcc-linaro-4.7 +bzr115000~uweigand~lp-1010826-4.7-p2/logs/armv7l-precise-cbuild335- ursa5-cortexa9hfr1/
So I think atomic-other-int.c is not a real regression.
Yes, this typically indicates a difference in which GDB version is installed on the test system ...
Let's ignore ursa5 as it's a PandaBoard ES. A recent example is: http://ex.seabright.co.nz/build/gcc-linaro-4.7+bzr115000~michaelh1~later-spl...
Different hosts but the same configuration: http://ex.seabright.co.nz/build/gcc-linaro-4.7+bzr114999/logs/armv7l-precise... http://ex.seabright.co.nz/build/gcc-linaro-4.7+bzr115000~michaelh1~later-spl...
as they're siblings.
The GDB record in the .log files seems the same except for different addresses. They both finish with:
0x0000866c 6 simulate_thread_fini = 1; 0x0000866e 6 simulate_thread_fini = 1; [Inferior 1 (process 22565) exited normally]
but the failing one adds:
/cbuild/slaves/ursa1/gcc-linaro-4.7+bzr115000~michaelh1~later-split-symrefs/gcc/gcc-linaro-4.7/gcc/testsuite/gcc.dg/simulate-thread/simulate-thread.gdb:11: Error in sourced command file: You can't do that without a process to debug. UNSUPPORTED: c-c++-common/simulate-thread/bitfields-3.c -O0 -g thread simulation test
Hmm.
-- Michael