Hi! On Tue, 26 Jan 2016 14:18:31 +0300 (MSK), Alexander Monakov wrote: > On Tue, 26 Jan 2016, Thomas Schwinge wrote: > > A very similar problem also exists for nvptx offloading (Nathan CCed), > > where we emit similar warnings (enabled by default). As nvptx offloading > > happens during link-time (not compile-time, as with hsa offloading), > > these don't affect GCC's compile tests, but need to be worked around in > > libgomp test cases. > > Can you mention some examples please? It's not clear to me what exactly you > have in mind. $ git grep -A3 warning upstream/gomp-4_0-branch -- gcc/config/nvptx/ upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c: warning_at (DECL_SOURCE_LOCATION (decl), 0, upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c- "OpenACC kernels construct will be executed " upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c- "sequentially; will by default avoid offloading " upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c- "to prevent data copy penalty"); -- upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c: warning_at (decl ? DECL_SOURCE_LOCATION (decl) : UNKNOWN_LOCATION, 0, upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c- dims[GOMP_DIM_VECTOR] upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c- ? "using vector_length (%d), ignoring %d" upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c- : "using vector_length (%d), ignoring runtime setting", -- upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c: warning_at (decl ? DECL_SOURCE_LOCATION (decl) : UNKNOWN_LOCATION, 0, upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c- "using num_workers (%d), ignoring %d", upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c- PTX_WORKER_LENGTH, dims[GOMP_DIM_WORKER]); upstream/gomp-4_0-branch:gcc/config/nvptx/nvptx.c- dims[GOMP_DIM_WORKER] = PTX_WORKER_LENGTH; (The latter two are present in trunk already.) Grüße Thomas