Hi Andreas! On Fri, 02 Oct 2015 13:58:55 +0200, Andreas Schwab <sch...@linux-m68k.org> wrote: > LAST_UPDATED: Fri Oct 2 02:31:25 UTC 2015 (revision 228367) > > Native configuration is aarch64-suse-linux-gnu
> === libgomp tests === > > > Running target unix > FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/abort-1.c > -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 output pattern test > FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/abort-3.c > -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 output pattern test > FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/abort-1.c > -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 output pattern test > FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/abort-3.c > -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 output pattern test Can you please show me what's in libgomp.log? Based on testing reports posted on <gcc-testresu...@gcc.gnu.org>, but only with your native aarch64-suse-linux-gnu configuration, these FAILs started to appear after my recent patch: <http://news.gmane.org/find-root.php?message_id=%3C87eghgthgm.fsf%40kepler.schwinge.homeip.net%3E>. The two regressed test cases use __builtin_printf instead of fprintf to stderr, but as far as I know, abort is to flush all open streams before process termination? (And it doesn, in some quick testing I've just done -- but I'm not set up to run the libgomp testsuite myself.) > === libgomp Summary === > > # of expected passes 4086 > # of unexpected failures 4 > # of expected failures 4 > # of unsupported tests 239 > Compiler version: 6.0.0 20151002 (experimental) [trunk revision 228367] (GCC) > Platform: aarch64-suse-linux-gnu > configure flags: --prefix=/usr --build=aarch64-suse-linux --enable-shared > --with-system-zlib CFLAGS='-O2 -g' CXXFLAGS='-O2 -g' Grüße, Thomas
signature.asc
Description: PGP signature
