This uses the patch I committed yesterday which introduces warp
broadcasts to implement the vector-single predication needed for
OpenACC. Outside a loop with vector parallelism, only one of the threads
representing a vector must execute, the others follow along. So we skip
the real work in
On Thu, 21 May 2015 13:57:00 +0200
Jakub Jelinek ja...@redhat.com wrote:
On Thu, May 21, 2015 at 01:42:11PM +0200, Bernd Schmidt wrote:
This uses the patch I committed yesterday which introduces warp
broadcasts to implement the vector-single predication needed for
OpenACC. Outside a loop
On Thu, May 21, 2015 at 01:42:11PM +0200, Bernd Schmidt wrote:
This uses the patch I committed yesterday which introduces warp broadcasts
to implement the vector-single predication needed for OpenACC. Outside a
loop with vector parallelism, only one of the threads representing a vector
must
On Thu, May 21, 2015 at 02:05:12PM +0100, Julian Brown wrote:
OpenACC handles function calls specially (calling them routines -- of
varying sorts, gang, worker, vector or seq, affecting where they can be
invoked from). The plan is that all threads will call such routines --
and then some
On Thu, 21 May 2015 14:38:19 +0100
Julian Brown jul...@codesourcery.com wrote:
On Thu, 21 May 2015 15:21:54 +0200
Jakub Jelinek ja...@redhat.com wrote:
On Thu, May 21, 2015 at 02:05:12PM +0100, Julian Brown wrote:
OpenACC handles function calls specially (calling them routines
-- of
On Thu, May 21, 2015 at 02:38:19PM +0100, Julian Brown wrote:
All functions will behave that way, or just some using some magic
attribute etc.? Say will newlib functions behave this way (math
functions, printf, ...)?
It's actually unclear at this point if regular functions are
On Thu, 21 May 2015 15:21:54 +0200
Jakub Jelinek ja...@redhat.com wrote:
On Thu, May 21, 2015 at 02:05:12PM +0100, Julian Brown wrote:
OpenACC handles function calls specially (calling them routines
-- of varying sorts, gang, worker, vector or seq, affecting where
they can be invoked
