]> git.ipfire.org Git - thirdparty/gcc.git/commit
[libgomp, testsuite, openacc] Remove -foffload=-w in reduction-[1-5].c
authorvries <vries@138bc75d-0d04-0410-961f-82ee72b054a4>
Fri, 11 Jan 2019 11:46:06 +0000 (11:46 +0000)
committervries <vries@138bc75d-0d04-0410-961f-82ee72b054a4>
Fri, 11 Jan 2019 11:46:06 +0000 (11:46 +0000)
commit8cccc21db7614d2df7c53a1900e8d49ab483a81e
tree870864189a4a1126a65b0ce68f164a93f42fdfe6
parent33db3d27337ad483289d1c86b726f816af5aea9a
[libgomp, testsuite, openacc] Remove -foffload=-w in reduction-[1-5].c

Before the commit "[libgomp, testsuite, openacc] Don't use const int for
dimensions", the "const int" construct was used to set launch dimensions in
reductions-[1-5].c.  In the case of -xc -O0, the const int is implemented as a
variable by the C front-end.  Consequently, the nvptx back-end generated
warnings that vector_length was overridden to be hard-coded, rather than left to
be set at runtime.  The test-cases silenced these warnings by switching off all
warnings in the accelerator compiler using "-foffload=-w".

Given that no warnings occur anymore, remove the "-foffload=-w" setting.

2019-01-11  Tom de Vries  <tdevries@suse.de>

* testsuite/libgomp.oacc-c-c++-common/reduction-1.c: Remove
-foffload=-w.
* testsuite/libgomp.oacc-c-c++-common/reduction-2.c: Same.
* testsuite/libgomp.oacc-c-c++-common/reduction-3.c: Same.
* testsuite/libgomp.oacc-c-c++-common/reduction-4.c: Same.
* testsuite/libgomp.oacc-c-c++-common/reduction-5.c: Same.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@267836 138bc75d-0d04-0410-961f-82ee72b054a4
libgomp/ChangeLog
libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-1.c
libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-2.c
libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-3.c
libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-4.c
libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-5.c