aboutsummaryrefslogtreecommitdiff
path: root/gcc/c/c-parser.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2019-01-07 08:10:56 +0000
committerTom de Vries <vries@gcc.gnu.org>2019-01-07 08:10:56 +0000
commitd495b5ccd252fdb01c70a73f145a008555b5a253 (patch)
treebf512a0d28ea5a6b009ba100e4b90493d4b5ea84 /gcc/c/c-parser.c
parent0024c32045a72ef45a64ab5673a2ba587978d9d1 (diff)
downloadgcc-d495b5ccd252fdb01c70a73f145a008555b5a253.zip
gcc-d495b5ccd252fdb01c70a73f145a008555b5a253.tar.gz
gcc-d495b5ccd252fdb01c70a73f145a008555b5a253.tar.bz2
[nvptx] Don't emit barriers for empty loops -- fix
When compiling an empty loop: ... long long v1; #pragma acc parallel num_gangs (640) num_workers(1) vector_length (128) #pragma acc loop for (v1 = 0; v1 < 20; v1 += 2) ; ... the compiler emits two subsequent bar.syncs. This triggers some bug on my quadro m1200 (I'm assuming in the ptxas/JIT compiler) that hangs the testcase. This patch works around the bug by doing an optimization: we detect that this is an empty loop (a forked immediately followed by a joining), and don't emit the barriers. The patch does not include the test-case yet, since vector_length (128) is not yet supported at this point. 2019-01-07 Tom de Vries <tdevries@suse.de> PR target/85381 * config/nvptx/nvptx.c (nvptx_process_pars): Don't emit barriers for empty loops. From-SVN: r267630
Diffstat (limited to 'gcc/c/c-parser.c')
0 files changed, 0 insertions, 0 deletions