Hi!
On 2019-11-14T18:22:39+0100, Jakub Jelinek wrote:
> On Thu, Nov 14, 2019 at 05:18:41PM +, Andrew Stubbs wrote:
>> On 14/11/2019 17:05, Jakub Jelinek wrote:
>> > On Thu, Nov 14, 2019 at 04:47:49PM +, Andrew Stubbs wrote:
>> > > This patch adds new libgomp tests to ensure that C "printf
On Thu, Nov 14, 2019 at 05:18:41PM +, Andrew Stubbs wrote:
> On 14/11/2019 17:05, Jakub Jelinek wrote:
> > On Thu, Nov 14, 2019 at 04:47:49PM +, Andrew Stubbs wrote:
> > > This patch adds new libgomp tests to ensure that C "printf" and Fortran
> > > "write" work correctly within offload ker
On 14/11/2019 17:05, Jakub Jelinek wrote:
On Thu, Nov 14, 2019 at 04:47:49PM +, Andrew Stubbs wrote:
This patch adds new libgomp tests to ensure that C "printf" and Fortran
"write" work correctly within offload kernels. Both should work for amdgcn,
but nvptx uses the libgfortran "minimal" mo
On 11/14/19 5:47 PM, Andrew Stubbs wrote:
This patch adds new libgomp tests to ensure that C "printf" and
Fortran "write" work correctly within offload kernels. Both should
work for amdgcn, but nvptx uses the libgfortran "minimal" mode which
lacks "write" support.
Can't you add something like
On Thu, Nov 14, 2019 at 04:47:49PM +, Andrew Stubbs wrote:
> This patch adds new libgomp tests to ensure that C "printf" and Fortran
> "write" work correctly within offload kernels. Both should work for amdgcn,
> but nvptx uses the libgfortran "minimal" mode which lacks "write" support.
So, do
