Re: [gomp4] libgomp: plugin for non-shared memory host execution

2014-02-20 Thread Thomas Schwinge
Hi! On Wed, 19 Feb 2014 17:10:15 +0100, I wrote: > $ gcc -m64 -Wall -Wextra -shared -o libgomp-plugin-host.so.1 > [...]/libgomp/plugin-host.c -fPIC -O -DDEBUG > > ..., and then set LIBGOMP_PLUGIN_PATH=$PWD in the environment. If putting plugins for several architectures into the same direct

Re: [gomp4] libgomp: plugin for non-shared memory host execution

2014-02-20 Thread Thomas Schwinge
Hi! On Wed, 19 Feb 2014 18:59:59 +0100, Jakub Jelinek wrote: > On Wed, Feb 19, 2014 at 09:49:20PM +0400, Ilya Verbin wrote: > > 2014-02-19 20:10 GMT+04:00 Thomas Schwinge : > > > Here is such a libgomp plugin plus the infrastructure for initial support > > > of non-shared memory host execution.

Re: [gomp4] libgomp: plugin for non-shared memory host execution (was: libgomp.c/target-1.c failing in fn2's GOMP_target_update)

2014-02-19 Thread Jakub Jelinek
On Wed, Feb 19, 2014 at 09:49:20PM +0400, Ilya Verbin wrote: > 2014-02-19 20:10 GMT+04:00 Thomas Schwinge : > > Here is such a libgomp plugin plus the infrastructure for initial support > > of non-shared memory host execution. Any comments? > > > > Grüße, > > Thomas > > This plugin looks good. >

Re: [gomp4] libgomp: plugin for non-shared memory host execution (was: libgomp.c/target-1.c failing in fn2's GOMP_target_update)

2014-02-19 Thread Ilya Verbin
2014-02-19 20:10 GMT+04:00 Thomas Schwinge : > Here is such a libgomp plugin plus the infrastructure for initial support > of non-shared memory host execution. Any comments? > > Grüße, > Thomas This plugin looks good. I think the function call in GOMP_target also should be replaced with a call

[gomp4] libgomp: plugin for non-shared memory host execution (was: libgomp.c/target-1.c failing in fn2's GOMP_target_update)

2014-02-19 Thread Thomas Schwinge
Hi! On Thu, 12 Dec 2013 12:31:40 +0100, I wrote: > On Fri, 8 Nov 2013 16:40:00 +0100, Jakub Jelinek wrote: > > [...], device 257 is just a temporary testing hack, [...] > > > [...], once we have at least one supported offloading target, > > hopefully we'll nuke device 257. > > Hmm, in contrast,