[Bug target/88981] [nvptx, openacc, libgomp] How to handle async regions without corresponding wait

2019-01-22 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88981 --- Comment #3 from Tom de Vries --- Thomas, any comments to add from OpenACC perspective? What is correct or desirable behaviour? Thanks, - Tom

[Bug target/89005] New: [nvptx, libgomp] Too much memory allocated in map_init

2019-01-23 Thread vries at gcc dot gnu.org
Component: target Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- Before "[nvptx] Remove use of CUDA unified memory in libgomp", in map_init we allocated a page-sized chunk of page-locked memory, which was used to p

[Bug target/89005] [nvptx, libgomp] Too much memory allocated in map_init

2019-01-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89005 --- Comment #1 from Tom de Vries --- Tentative patch to remove initial element: ... diff --git a/libgomp/plugin/plugin-nvptx.c b/libgomp/plugin/plugin-nvptx.c index ff90b67cb86..cbabc8dba96 100644 --- a/libgomp/plugin/plugin-nvptx.c +++ b/libgomp

[Bug target/88941] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for empty asynchronous parallel

2019-01-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88941 --- Comment #3 from Tom de Vries --- Author: vries Date: Wed Jan 23 08:16:42 2019 New Revision: 268177 URL: https://gcc.gnu.org/viewcvs?rev=268177&root=gcc&view=rev Log: [nvptx, libgomp] Fix assert (!s->map->active) in map_fini There are curren

[Bug target/87835] nvptx offloading: libgomp.oacc-c-c++-common/asyncwait-1.c execution test intermittently fails at -O2

2019-01-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87835 --- Comment #5 from Tom de Vries --- Author: vries Date: Wed Jan 23 08:16:11 2019 New Revision: 268176 URL: https://gcc.gnu.org/viewcvs?rev=268176&root=gcc&view=rev Log: [nvptx, libgomp] Fix map_push The map field of a struct ptx_stream is a FI

[Bug target/88939] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for synchronous parallel with abort

2019-01-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88939 --- Comment #3 from Tom de Vries --- Author: vries Date: Wed Jan 23 08:16:42 2019 New Revision: 268177 URL: https://gcc.gnu.org/viewcvs?rev=268177&root=gcc&view=rev Log: [nvptx, libgomp] Fix assert (!s->map->active) in map_fini There are curren

[Bug target/87835] nvptx offloading: libgomp.oacc-c-c++-common/asyncwait-1.c execution test intermittently fails at -O2

2019-01-23 Thread vries at gcc dot gnu.org
|--- |FIXED Assignee|unassigned at gcc dot gnu.org |vries at gcc dot gnu.org Target Milestone|--- |9.0 --- Comment #6 from Tom de Vries --- Patch and test-case committed, marking resolved fixed.

[Bug target/88939] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for synchronous parallel with abort

2019-01-23 Thread vries at gcc dot gnu.org
|--- |FIXED Assignee|unassigned at gcc dot gnu.org |vries at gcc dot gnu.org Target Milestone|--- |9.0 --- Comment #4 from Tom de Vries --- Patch committed. Test-case that triggered this PR is already in the sources, but unfortunately we don&#

[Bug target/88941] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for empty asynchronous parallel

2019-01-23 Thread vries at gcc dot gnu.org
|--- |FIXED Assignee|unassigned at gcc dot gnu.org |vries at gcc dot gnu.org Target Milestone|--- |9.0 --- Comment #4 from Tom de Vries --- Patch and test-case committed, marking resolved fixed.

[Bug target/88946] [nvptx, openacc, libgomp] cuMemAlloc error for two empty asynchronous parallels

2019-01-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88946 Tom de Vries changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |vries at gcc dot gnu.org Target

[Bug target/88946] [nvptx, openacc, libgomp] cuMemAlloc error for two empty asynchronous parallels

2019-01-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88946 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug testsuite/89034] New: [libgomp, openacc] dg-shouldfail in abort-1.c allows libgomp asserts to go undetected

2019-01-24 Thread vries at gcc dot gnu.org
Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- See "[nvptx, openacc, libgomp] Assertion `!s->map->active' failed for synchronous parallel with a

[Bug testsuite/89034] [libgomp, openacc] dg-shouldfail in abort-1.c allows libgomp asserts to go undetected

2019-01-24 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89034 Tom de Vries changed: What|Removed |Added Keywords||openacc CC|

[Bug testsuite/89034] [libgomp, openacc] dg-shouldfail in abort-1.c allows libgomp asserts to go undetected

2019-01-24 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89034 --- Comment #2 from Tom de Vries --- Thomas, is this replacement for abort-1.c OK for trunk? If so, I'll commit this, otherwise, I'll commit this as abort-nvptx.c or some such. Thanks - Tom

[Bug libgomp/87834] nvptx offloading: "WARNING: program timed out" for libgomp.fortran/target2.f90 execution test at -O0, -O1

2019-01-24 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87834 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libgomp/81691] libgomp.fortran/target2.f90 fails for nvptx at -O0 and -O1

2019-01-24 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81691 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libbacktrace/89136] libbacktrace/elf.c:2941: suspicious assignment

2019-01-31 Thread vries at gcc dot gnu.org
|ASSIGNED Last reconfirmed||2019-01-31 Assignee|unassigned at gcc dot gnu.org |vries at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Tom de Vries --- https://gcc.gnu.org/ml/gcc-patches/2019-01

[Bug libbacktrace/89136] libbacktrace/elf.c:2941: suspicious assignment

2019-01-31 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136 --- Comment #3 from Tom de Vries --- Author: vries Date: Thu Jan 31 12:17:32 2019 New Revision: 268419 URL: https://gcc.gnu.org/viewcvs?rev=268419&root=gcc&view=rev Log: [libbacktrace] Fix .gnu_debugaltlink build-id check The 'debugaltlink_name

[Bug libbacktrace/89136] libbacktrace/elf.c:2941: suspicious assignment

2019-01-31 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136 Tom de Vries changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libbacktrace/89136] libbacktrace/elf.c:2941: suspicious assignment

2019-01-31 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136 --- Comment #6 from Tom de Vries --- (In reply to Jakub Jelinek from comment #4) > Shouldn't we have a warning for this =+ vs. += case (of course, =- is fine)? I found PR45358 - "Diagnostic could be issued for old C style a =+ b and similar case

[Bug c/45358] Diagnostic could be issued for old C style a =+ b and similar cases

2019-01-31 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45358 Tom de Vries changed: What|Removed |Added CC||vries at gcc dot gnu.org --- Comment #5

[Bug other/78063] libbacktrace fails to handle cross CU DW_AT_abstract_origin

2019-02-06 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78063 Tom de Vries changed: What|Removed |Added CC||vries at gcc dot gnu.org --- Comment #4

[Bug libbacktrace/78063] libbacktrace fails to handle cross CU DW_AT_abstract_origin

2019-02-07 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78063 --- Comment #7 from Tom de Vries --- Author: vries Date: Fri Feb 8 05:55:44 2019 New Revision: 268663 URL: https://gcc.gnu.org/viewcvs?rev=268663&root=gcc&view=rev Log: [libbacktrace] Handle DW_FORM_ref_addr Add handling of the DW_FORM_ref_add

[Bug libbacktrace/78063] libbacktrace fails to handle cross CU DW_AT_abstract_origin

2019-02-08 Thread vries at gcc dot gnu.org
|--- |FIXED Assignee|unassigned at gcc dot gnu.org |vries at gcc dot gnu.org Target Milestone|--- |9.0 --- Comment #8 from Tom de Vries --- Patch committed. Test-case patch submitted ( https://gcc.gnu.org/ml/gcc-patches/2019-02/msg00432.html

[Bug libbacktrace/87653] Calling null pointer in multi-threaded applications

2019-02-08 Thread vries at gcc dot gnu.org
||2019-02-08 CC||vries at gcc dot gnu.org Ever confirmed|0 |1

[Bug target/85296] New: [nvptx] pr85244-1.c execution failure

2018-04-09 Thread vries at gcc dot gnu.org
Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- We see failures for this testcase: ... PASS: gcc.dg/torture/pr85244-1.c -O0 (test for excess errors) FAIL: gcc.dg/torture/pr85244-1.c -O0 execution test PASS: gcc.dg/torture

[Bug target/85296] [nvptx] pr85244-1.c execution failure

2018-04-09 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85296 --- Comment #1 from Tom de Vries --- Created attachment 43882 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43882&action=edit Tentative patch

[Bug target/84041] [nvptx] Hang in for-3.c

2018-04-09 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84041 Tom de Vries changed: What|Removed |Added Keywords||wrong-code Status|UNCONFIRMED

[Bug target/84041] [nvptx] Hang in for-3.c

2018-04-09 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84041 --- Comment #5 from Tom de Vries --- Author: vries Date: Mon Apr 9 13:22:00 2018 New Revision: 259233 URL: https://gcc.gnu.org/viewcvs?rev=259233&root=gcc&view=rev Log: [nvptx] Add memory_barrier insn 2018-04-09 Tom de Vries PR tar

[Bug testsuite/85303] New: [testsuite, libgomp] dg-message not supported

2018-04-09 Thread vries at gcc dot gnu.org
: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- In libgomp test-cases, dg-error, dg-warning and dg-bogus can be used, but dg-message not.

[Bug testsuite/85303] [testsuite, libgomp] dg-message not supported

2018-04-09 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85303 Tom de Vries changed: What|Removed |Added CC||jakub at gcc dot gnu.org Severi

[Bug target/85341] New: [nvptx] Implement atomic load

2018-04-11 Thread vries at gcc dot gnu.org
Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- [ Follow-up PR of PR84041 - "[nvptx] Hang in for-3.c" ] Atm the nvptx port does not define an atomic load insn. Consequently, it goes through the fallback scenario in expand_a

[Bug target/84041] [nvptx] Hang in for-3.c

2018-04-11 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84041 --- Comment #6 from Tom de Vries --- (In reply to Tom de Vries from comment #4) > A conservative fix is to define the memory_barrier insn as membar.sys. Filed PR85341 - "[nvptx] Implement atomic load" to fix this more optimally.

[Bug target/84041] [nvptx] Hang in for-3.c

2018-04-11 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84041 Tom de Vries changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/85204] [nvptx] infinite loop generated

2018-04-11 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85204 Tom de Vries changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/85296] [nvptx] pr85244-1.c execution failure

2018-04-12 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85296 --- Comment #2 from Tom de Vries --- Author: vries Date: Thu Apr 12 07:17:29 2018 New Revision: 259337 URL: https://gcc.gnu.org/viewcvs?rev=259337&root=gcc&view=rev Log: [nvptx] Fix handling of extern var with flexible array member 2018-04-12

[Bug target/85296] [nvptx] pr85244-1.c execution failure

2018-04-12 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85296 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/85296] [nvptx] pr85244-1.c execution failure

2018-04-12 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85296 Tom de Vries changed: What|Removed |Added Target Milestone|--- |8.0

[Bug target/85246] [og7, nvptx, openacc] gemm.f90 fails with -mlong-vector-in-workers

2018-04-12 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85246 --- Comment #2 from Tom de Vries --- (In reply to Tom de Vries from comment #1) > I went through a couple of cycles of minimizing the failure, seeing > something suspicious, modifying by hand or writing a tentative patch, but > every time I went

[Bug target/85246] [og7, nvptx, openacc] gemm.f90 fails with -mlong-vector-in-workers

2018-04-12 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85246 --- Comment #3 from Tom de Vries --- (In reply to Tom de Vries from comment #1) > I went through a couple of cycles of minimizing the failure, seeing > something suspicious, modifying by hand or writing a tentative patch, but > every time I went

[Bug target/85246] [og7, nvptx, openacc] gemm.f90 fails with -mlong-vector-in-workers

2018-04-12 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85246 --- Comment #4 from Tom de Vries --- Created attachment 43920 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43920&action=edit 0001-nvptx-Simplifly-logic-in-nvptx_single.patch NFC patch to make fix easier

[Bug target/85246] [og7, nvptx, openacc] gemm.f90 fails with -mlong-vector-in-workers

2018-04-12 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85246 --- Comment #5 from Tom de Vries --- Created attachment 43921 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43921&action=edit 0002-nvptx-Fix-propagation-of-branch-cond-in-vw-neutered-code.patch Tentative fix.

[Bug target/85246] [og7, nvptx, openacc] gemm.f90 fails with -mlong-vector-in-workers

2018-04-12 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85246 Tom de Vries changed: What|Removed |Added Keywords||wrong-code Status|UNCONFIRMED

[Bug target/85381] New: [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128

2018-04-12 Thread vries at gcc dot gnu.org
: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- When running parallel-loop-1.c with this patch, it hangs: ... diff --git a/libgomp/testsuite/libgomp.oacc-c-c++-common

[Bug libgomp/85411] New: [openacc] Move GOMP_OPENACC_DIM parsing out of nvptx plugin

2018-04-16 Thread vries at gcc dot gnu.org
Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- As mentioned here ( https://gcc.gnu.org/ml/gcc-patches/2017-02/msg01020.html ): ... the

[Bug libgomp/85129] [openacc] Document GOMP_OPENACC_DIM

2018-04-16 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85129 --- Comment #4 from Tom de Vries --- (In reply to Thomas Schwinge from comment #3) > (In reply to Tom de Vries from comment #2) > > GOMP_OPENACC_DIM seems to be the odd one here, and we should document > > the non-standard behaviour that it suppo

[Bug libgomp/85411] [openacc] Move GOMP_OPENACC_DIM parsing out of nvptx plugin

2018-04-16 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85411 Tom de Vries changed: What|Removed |Added Keywords||patch --- Comment #1 from Tom de Vries -

[Bug libgomp/85129] [openacc] Document GOMP_OPENACC_DIM

2018-04-16 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85129 --- Comment #5 from Tom de Vries --- (In reply to Tom de Vries from comment #0) > I. trunk > > The GOMP_OPENACC_DIM environment variable is not documented (it should have > an entry in libgomp.texi at 'OpenACC Environment Variables'). Atm, in t

[Bug lto/85422] New: [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-16 Thread vries at gcc dot gnu.org
Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org CC: marxin at gcc dot gnu.org Target Milestone: --- When compiling this program: ... int main (void) { #pragma acc parallel #pragma acc loop for (int

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-16 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 Tom de Vries changed: What|Removed |Added Keywords||openacc --- Comment #1 from Tom de Vries

[Bug middle-end/84955] [7/8 Regression] Incorrect OpenACC tile expansion

2018-04-16 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84955 --- Comment #7 from Tom de Vries --- (In reply to cesar from comment #6) > It should be noted that GCC also chokes with any empty OpenACC loop in > general. Filed as PR85422 - [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

[Bug middle-end/84955] [7/8 Regression] Incorrect OpenACC tile expansion

2018-04-16 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84955 --- Comment #8 from Tom de Vries --- Author: vries Date: Mon Apr 16 18:01:09 2018 New Revision: 259406 URL: https://gcc.gnu.org/viewcvs?rev=259406&root=gcc&view=rev Log: [openacc] Fix ICE when compiling tile loop containing infinite loop 2018-0

[Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128

2018-04-17 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381 --- Comment #2 from Tom de Vries --- I minimized this failure, and ran into PR 80035/81069, so I've backported the fix from trunk: https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00774.html

[Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128

2018-04-17 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381 --- Comment #3 from Tom de Vries --- (In reply to Tom de Vries from comment #2) > I minimized this failure, and ran into PR 80035/81069, so I've backported > the fix from trunk: https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00774.html With that

[Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128

2018-04-17 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381 --- Comment #4 from Tom de Vries --- This looks like a JIT bug, but with this tentative patch: ... diff --git a/gcc/config/nvptx/nvptx.c b/gcc/config/nvptx/nvptx.c index 8c478c874bd..ac394ee1ae6 100644 --- a/gcc/config/nvptx/nvptx.c +++ b/gcc/con

[Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128

2018-04-17 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381 --- Comment #5 from Tom de Vries --- (In reply to Tom de Vries from comment #4) > This looks like a JIT bug, but with this tentative patch: ... > no barriers are generated, and the minimized testcase passes. And the original test-case passes.

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-17 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 Tom de Vries changed: What|Removed |Added Known to fail||6.4.0, 7.3.0 --- Comment #2 from Tom de V

[Bug lto/71959] [OpenACC] lto1: ICE in inline_read_section, at ipa-fnsummary.c:3314

2018-04-17 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71959 Tom de Vries changed: What|Removed |Added CC||vries at gcc dot gnu.org

[Bug target/85445] New: [nvptx, openacc] Calls to worker and vector routine broken

2018-04-18 Thread vries at gcc dot gnu.org
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- og7 test-case ref-1.C fails in execution when run with trunk: ... /* { dg-do run } */ extern "C" int printf (char const *, ...); #

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 --- Comment #4 from Tom de Vries --- Created attachment 43975 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43975&action=edit libgomp.log

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 --- Comment #5 from Tom de Vries --- Created attachment 43976 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43976&action=edit compile.log -save-temps -v output. Contains lto1 invocation.

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 --- Comment #6 from Tom de Vries --- Created attachment 43978 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43978&action=edit configure lines

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 Tom de Vries changed: What|Removed |Added CC||tschwinge at gcc dot gnu.org --- Comment

[Bug lto/85451] New: [offloading] Improve lto-wrapper error message when not finding mkoffload

2018-04-18 Thread vries at gcc dot gnu.org
: enhancement Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org CC: marxin at gcc dot gnu.org Target Milestone: --- When using an installed host/offloading compiler, you may run into this error

[Bug lto/85451] [offloading] Improve lto-wrapper error message when not finding mkoffload

2018-04-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85451 --- Comment #1 from Tom de Vries --- Created attachment 43980 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43980&action=edit Tentative patch

[Bug lto/85451] [offloading] Improve lto-wrapper error message when not finding mkoffload

2018-04-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85451 --- Comment #2 from Tom de Vries --- (In reply to Tom de Vries from comment #1) > Created attachment 43980 [details] > Tentative patch Improved error message: ... $ ./install/bin/x86_64-pc-linux-gnu-gcc -fopenacc test.c lto-wrapper: fatal error:

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 --- Comment #8 from Tom de Vries --- (In reply to Tom de Vries from comment #7) > (In reply to Richard Biener from comment #3) > > flags? A simple ./xgcc -fopenacc doesn't reproduce it. With my GCC 7 > > install I see > > > > lto-wrapper: fata

[Bug lto/85451] [offloading] Improve lto-wrapper error message when not finding mkoffload

2018-04-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85451 --- Comment #3 from Tom de Vries --- (In reply to Tom de Vries from comment #0) > ... > $ ./install/bin/x86_64-pc-linux-gnu-gcc -fopenacc test.c \ > -B $(pwd > -P)/install/offload-nvptx-none/libexec/gcc/x86_64-pc-linux-gnu/8.0.1 > mkoffload: fa

[Bug target/85220] [meta-bug, nvptx] Run trunk with og7 openacc testcases and analyze execution failures

2018-04-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85220 --- Comment #3 from Tom de Vries --- Filed: - PR85221 "[openacc] ICE in install_var_field, at omp-low.c:657" - PR85445 "[nvptx, openacc] Calls to worker and vector routine broken" and updated a few existing PRs. There are lots of execution fai

[Bug c/85465] New: [og7, openacc] ICE in mark_vars_oacc_gangprivate, at c/c-parser.c:14213

2018-04-19 Thread vries at gcc dot gnu.org
: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- $ cat bug.c int main (void) { #pragma acc parallel foo (); return 0; } $ ./install/bin/gcc bug.c -fopenacc bug.c: In

[Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128

2018-04-19 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381 --- Comment #6 from Tom de Vries --- Created attachment 43992 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43992&action=edit tentative patch (In reply to Tom de Vries from comment #4) > This looks like a JIT bug, but with this tentative

[Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128

2018-04-19 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381 --- Comment #7 from Tom de Vries --- For this example: ... #define n 1024 int main (void) { #pragma acc parallel vector_length(128) { #pragma acc loop vector for (int i = 0; i < n; i++) ; #pragma acc loop vector for (i

[Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128

2018-04-19 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381 --- Comment #8 from Tom de Vries --- (In reply to Tom de Vries from comment #6) > Created attachment 43992 [details] > tentative patch Tested libgomp on og7 build with quadro m1200, no issues found.

[Bug target/85445] [nvptx, openacc] Calls to worker and vector routine broken

2018-04-20 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85445 --- Comment #1 from Tom de Vries --- (In reply to Tom de Vries from comment #0) > og7 test-case ref-1.C fails in execution when run with trunk: At -O2, due to the call to routine Worker. The Vector routine is inlined, due to missing noinline,noc

[Bug target/85445] [nvptx, openacc] Calls to worker and vector routine broken

2018-04-20 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85445 --- Comment #2 from Tom de Vries --- (In reply to Tom de Vries from comment #1) > The initialization of the stack is done in thread W0V0, but the stack is > read in WAVA mode, so it's reading uninitialized stack memory in all but > the W0V0 thre

[Bug target/85445] [nvptx, openacc] Calls to worker and vector routine broken

2018-04-20 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85445 --- Comment #3 from Tom de Vries --- Author: vries Date: Fri Apr 20 13:46:07 2018 New Revision: 259523 URL: https://gcc.gnu.org/viewcvs?rev=259523&root=gcc&view=rev Log: [nvptx] Fix calls to vector and worker routines 2018-04-20 Nathan Sidwell

[Bug target/85445] [nvptx, openacc] Calls to worker and vector routine broken

2018-04-20 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85445 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128

2018-04-20 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381 Tom de Vries changed: What|Removed |Added Attachment #43992|0 |1 is obsolete|

[Bug target/85486] New: [og7, nvptx] ref-1.C fails with vector length 128

2018-04-20 Thread vries at gcc dot gnu.org
Component: target Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- Minimal example: ... /* { dg-do run } */ extern "C" int printf (char const *, ...); #pragma acc routine vector void __attribute__((noinline, noclone)) Vector

[Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128

2018-04-21 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381 Tom de Vries changed: What|Removed |Added Keywords||openacc Status|UNCONFIRMED

[Bug target/85220] [meta-bug, nvptx] Run trunk with og7 openacc testcases and analyze execution failures

2018-04-21 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85220 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/85486] [og7, nvptx] ref-1.C fails with vector length 128

2018-04-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85486 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 --- Comment #10 from Tom de Vries --- Created attachment 44006 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44006&action=edit Adjusted patch with testcase (In reply to Richard Biener from comment #9) > adjusted patch: Added testcase.

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-23 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 Tom de Vries changed: What|Removed |Added Keywords||ice-on-valid-code, patch --- Comment #11

[Bug target/85519] New: [nvptx, openacc, openmp, testsuite] Recursive tests may fail due to thread stack limit

2018-04-24 Thread vries at gcc dot gnu.org
Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- I. Consider the following openacc program containing a recursive function: ... #pragma acc routine seq static

[Bug target/85519] [nvptx, openacc, openmp, testsuite] Recursive tests may fail due to thread stack limit

2018-04-25 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85519 --- Comment #1 from Tom de Vries --- (In reply to Tom de Vries from comment #0) > All these solutions work until the next failure shows up. It would be nice > to fix this more definitely in some way, but I'm not sure how. We could try to figure

[Bug target/85519] [nvptx, openacc, openmp, testsuite] Recursive tests may fail due to thread stack limit

2018-04-25 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85519 Tom de Vries changed: What|Removed |Added Keywords||openacc, openmp, patch Severity

[Bug testsuite/85527] New: [openacc] atomic_capture-1.{c,f90} undefined behaviour

2018-04-25 Thread vries at gcc dot gnu.org
Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- I. Consider this test-case, minimized from atomic_capture-1.f90: ... program main real fgot, fexp, ftmp integer, parameter :: N = 32 fgot = 1234.0 fexp

[Bug target/85519] [nvptx, openacc, openmp, testsuite] Recursive tests may fail due to thread stack limit

2018-04-26 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85519 --- Comment #3 from Tom de Vries --- Author: vries Date: Thu Apr 26 13:26:09 2018 New Revision: 259674 URL: https://gcc.gnu.org/viewcvs?rev=259674&root=gcc&view=rev Log: [nvptx, libgomp, testsuite] Reduce recursion depth in declare_target-{1,2}.

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-26 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 --- Comment #12 from Tom de Vries --- Author: vries Date: Thu Apr 26 13:26:25 2018 New Revision: 259675 URL: https://gcc.gnu.org/viewcvs?rev=259675&root=gcc&view=rev Log: [lto] Fixup loops before lto write-out 2018-04-26 Richard Biener

[Bug target/84025] [nvptx] Don't generate branch-around-nothing

2018-04-26 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84025 --- Comment #2 from Tom de Vries --- Author: vries Date: Thu Apr 26 13:26:38 2018 New Revision: 259676 URL: https://gcc.gnu.org/viewcvs?rev=259676&root=gcc&view=rev Log: [nvptx] Fix branch-around-nothing 2018-04-26 Tom de Vries PR t

[Bug target/84952] [nvptx] bar.sync generated in divergent code

2018-04-26 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84952 --- Comment #11 from Tom de Vries --- Author: vries Date: Thu Apr 26 13:26:48 2018 New Revision: 259677 URL: https://gcc.gnu.org/viewcvs?rev=259677&root=gcc&view=rev Log: [nvptx] Verify bar.sync position 2018-04-26 Tom de Vries PR t

[Bug libgomp/84020] [nvptx] Add GOMP_NVPTX_JIT=-O[0-4] in nvptx libgomp plugin

2018-04-26 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84020 --- Comment #1 from Tom de Vries --- Author: vries Date: Thu Apr 26 13:27:04 2018 New Revision: 259678 URL: https://gcc.gnu.org/viewcvs?rev=259678&root=gcc&view=rev Log: [nvptx, libgomp] Add GOMP_NVPTX_JIT=-O[0-4] in nvptx libgomp plugin 2018-0

[Bug target/85519] [nvptx, openacc, openmp, testsuite] Recursive tests may fail due to thread stack limit

2018-04-26 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85519 --- Comment #4 from Tom de Vries --- Committed to trunk. Approved for 8.2. [ 8.1 release is targeted for Wednesday, May 2nd. ]

[Bug lto/85422] [openacc] ICE at cfgloop.c:468: segfault in flow_loops_find

2018-04-26 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422 Tom de Vries changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libgomp/84020] [nvptx] Add GOMP_NVPTX_JIT=-O[0-4] in nvptx libgomp plugin

2018-04-26 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84020 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/84025] [nvptx] Don't generate branch-around-nothing

2018-04-26 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84025 Tom de Vries changed: What|Removed |Added Target Milestone|--- |9.0 --- Comment #3 from Tom de Vries ---

[Bug target/84025] [nvptx] Don't generate branch-around-nothing

2018-04-26 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84025 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug testsuite/85527] [openacc] atomic_capture-1.{c,f90} undefined behaviour

2018-04-27 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85527 --- Comment #1 from Tom de Vries --- Author: vries Date: Fri Apr 27 22:11:12 2018 New Revision: 259733 URL: https://gcc.gnu.org/viewcvs?rev=259733&root=gcc&view=rev Log: [openacc, testsuite] Fix undefined behaviour in atomic_capture-1.f90 2018-

[Bug testsuite/85527] [openacc] atomic_capture-1.{c,f90} undefined behaviour

2018-04-29 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85527 --- Comment #2 from Tom de Vries --- Author: vries Date: Sun Apr 29 10:26:56 2018 New Revision: 259748 URL: https://gcc.gnu.org/viewcvs?rev=259748&root=gcc&view=rev Log: [openacc, testsuite] Fix undefined behaviour in atomic_capture-1.c 2018-04

<    1   2   3   4   5   6   7   8   9   10   >