Hi, On Thu, Apr 26 2018, Thomas Schwinge wrote: > Hi Martin! > > On Wed, 25 Apr 2018 15:56:26 +0200, Martin Jambor <mjam...@suse.cz> wrote: >> On Thu, Apr 19 2018, Thomas Schwinge wrote: >> > * testsuite/libgomp.oacc-fortran/error_stop-1.f: New file. >> > * testsuite/libgomp.oacc-fortran/error_stop-2.f: Likewise. >> > * testsuite/libgomp.oacc-fortran/error_stop-3.f: Likewise. >> > * testsuite/libgomp.oacc-fortran/stop-1.f: Likewise. >> > * testsuite/libgomp.oacc-fortran/stop-2.f: Likewise. >> > * testsuite/libgomp.oacc-fortran/stop-3.f: Likewise. >> >> The "output pattern test" part of all of these new testcases fail on my >> HSA tester even though no HSAIL is generated for them > > > Is there anything "special" in your HSA machine regarding stdout/stderr? > How are you testing GCC there: native testing or some non-standard *.exp > file, for example? Does using strace give any idea where which part of > the output is going? >
this issue was caused on my side, because the ROCm runtime produced some debug output to stderr upon initialization. I have backported a fix for this to my packages and the issues is gone. It is still slightly intriguing, because the patterns dg-output was searching for were present there also before, the debug stuff did not appear in the middle of them or anything, so I do not quite understand why the tests were failing before, but it is probably not worth investigating. Let's hope the periodic run next week will agree with my manual tests. Sorry for the noise, Martin
