Some of the new libgomp tests fail initially for this target when tested
with a simulator, for various reasons.  This PR tracks them.
Running /home/hp/combined/combined/libgomp/testsuite/libgomp.c/c.exp ...
FAIL: libgomp.c/appendix-a/a.15.1.c execution test
WARNING: program timed out.
FAIL: libgomp.c/appendix-a/a.18.1.c execution test
WARNING: program timed out.
FAIL: libgomp.c/appendix-a/a.2.1.c execution test
WARNING: program timed out.
FAIL: libgomp.c/appendix-a/a.39.1.c execution test
FAIL: libgomp.c/barrier-1.c execution test
WARNING: libgomp.c/critical-1.c compilation failed to produce executable
WARNING: libgomp.c/lib-1.c compilation failed to produce executable
WARNING: libgomp.c/loop-1.c compilation failed to produce executable
FAIL: libgomp.c/loop-2.c (test for excess errors)
WARNING: libgomp.c/loop-2.c compilation failed to produce executable
FAIL: libgomp.c/omp-loop03.c execution test
FAIL: libgomp.c/omp_hello.c execution test
FAIL: libgomp.c/omp_orphan.c execution test
FAIL: libgomp.c/omp_workshare1.c execution test
FAIL: libgomp.c/omp_workshare2.c execution test
FAIL: libgomp.c/omp_workshare4.c execution test
WARNING: libgomp.c/ordered-1.c compilation failed to produce executable
WARNING: libgomp.c/ordered-2.c compilation failed to produce executable
WARNING: libgomp.c/sections-1.c compilation failed to produce executable
WARNING: libgomp.c/single-1.c compilation failed to produce executable

Some tests fail due to an invalid access:
libgomp.c/appendix-a/a.15.1.c
libgomp.c/omp_hello.c
libgomp.c/omp_orphan.c
libgomp.c/omp_workshare1.c
libgomp.c/omp_workshare2.c
libgomp.c/omp_workshare4.c
where the .log entry looks like this:
core: 1 byte write to unmapped address 0x3d800000 at 0xa797e^M
program stopped with signal 11.^M
FAIL: libgomp.c/appendix-a/a.15.1.c execution test

Some tests just time out.  This may or may not be due to incorrect or limited
thread support (yes, there is *some* support) in the simulator.
libgomp.c/appendix-a/a.18.1.c
libgomp.c/appendix-a/a.2.1.c
libgomp.c/appendix-a/a.39.1.c

One test fails due to an unimplemented syscall in the simulator:
libgomp.c/barrier-1.c
The .log:
Unimplemented syscall: 162 (0x3dfffdb4, 0x0, 0xddd84, 0xf4240, 0x0, 0x98d52)^M
program stopped with signal 4.^M
FAIL: libgomp.c/barrier-1.c execution test

Some test fail due to a missing sync library function or missing open-code
implementation of __sync_lock_test_and_set_4:
libgomp.c/loop-1.c
libgomp.c/loop-2.c
libgomp.c/ordered-1.c
libgomp.c/ordered-2.c
libgomp.c/sections-1.c
libgomp.c/single-1.c
libgomp.c/critical-1.c
Curiously enough *some* of these pass the "excess errors" test.  The .log entry
looks like this:
/tmp/ccMhq34N.o: In function `function':critical-1.c:(.text+0x20): undefined reference to `__sync_lock_test_and_set_4'^M
collect2: ld returned 1 exit status^M
compiler exited with status 1

One fail for some other reason, possibly simulator-thread-implementation-related:
PASS: libgomp.c/omp-loop03.c (test for excess errors)
^M
libgomp: Thread creation failed: Resource temporarily unavailable^M
Thread 105 exited with status 1^M
program stopped with signal 4.^M
FAIL: libgomp.c/omp-loop03.c execution test

I assign this PR to myself so nobody is tempted to act on it.