On 10/29/14 17:55, Bernd Schmidt wrote:
Thanks! I've pinged some of the preliminary patches that went unapproved
up to this point.
Thanks.
One leftover issue, discussed in the [0/11] mail - what amount of
documentation is appropriate for this, given that we don't want to
support using this as anything other than an offload compiler? Should I
still add all the standard invoke.texi/gccint.texi pieces?
I'm still not sure here. nvptx is quite a bit different than anything
we've done in the past and I'm not sure how much of the traditional
stuff we want to document vs on the other end how much of the special
stuff we want to document. I simply don't know.
I notice that you've got some OpenMP bits (write_as_kernel). Are y'all
doing any testing with OpenMP or is that an artifact of layering OpenACC
on top of the OpenMP infrastructure?
The distinction between .kernel and .func is really not to do with
either - only .kernels are callable from the host, and only .funcs are
callable from within ptx code.
Ok. Thanks for clarifying.
jeff
