On 2015-05-04 4:32 AM, Thomas Schwinge wrote:
Dave, would you please test the following patch, and report the
regression status compared to before r222620? (Compared to your existing
r222021 results, as posted in the PR, for example.)
With patch, we have the following fails on hppa2.0w-hp-hpux11.11:
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/lib-3.c
-DACC_DEVICE_TYPE_host
=1 -DACC_MEM_SHARED=1 output pattern test, is
libgomp: no device found
, should match device [0-9]+\([0-9]+\) is initialized
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/lib-42.c
-DACC_DEVICE_TYPE_hos
t=1 -DACC_MEM_SHARED=1 output pattern test, is , should match
\[[0-9a-fA-FxX]+,2
56\] is not mapped
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/lib-62.c
-DACC_DEVICE_TYPE_hos
t=1 -DACC_MEM_SHARED=1 output pattern test, is , should match invalid size
Running /test/gnu/gcc/gcc/libgomp/testsuite/libgomp.oacc-c++/c++.exp ...
FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/lib-3.c
-DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 output pattern test, is
libgomp: no device found
, should match device [0-9]+\([0-9]+\) is initialized
FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/lib-42.c
-DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 output pattern test, is ,
should match \[[0-9a-fA-FxX]+,256\] is not mapped
FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/lib-62.c
-DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 output pattern test, is ,
should match invalid size
Note this is a 32-bit build and not the 64-bit build reported in PR.
However, I would expect similar
printf support. Don't have a 64-bit build handy.
Dave
--
John David Anglin dave.ang...@bell.net
