https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80759
--- Comment #1 from Daniel Santos <daniel.santos at pobox dot com> --- (In reply to Rainer Orth from comment #0) > It seems to me that ms-sysv.exp is seriously misguided in trying to do all > its compilations manually instead of using > dg-test/dg-runtest/gcc_target_compile > which whould nicely avoid all those issues. Well, this was my introduction to DejaGnu and the test harness. I found that none of these support doing a build when there is more than one object file -- in my case, I'm linking the output of both ms-sysv.c and do_test.S. However, this test started out with multiple .c files and I was able to reduce it down to one. I'm going to see if there's a way to cleanly do my assembly inline and reduce it down to a single translation unit which gc-runtest, et. al. will work with. Otherwise, I'll have to fix the .struct, CFLAGS and multiple warnings. If I'm wrong about the single object file thing, please point me in the right direction. > The new gcc.target/x86_64/abi/ms-sysv tests FAIL in various e.g. on > i386-pc-solaris2.* > and i686-pc-linux-gnu: > > * In those 32-bit-default configurations, the 32-bit multilib is skipped as > unsupported as expected (although the UNSUPPORTED entry in gcc.sum occurs > e.g. 45 times for -j48 testing instead of only once), Sadly, I discovered that by not using the standard test functions that I had to cook up my own parallelism scheme, otherwise all of my tests would run once for each -j<job>! I think that this issue is fixable though.
