This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: trying out openacc 2.0

Mark Farnell wrote:
> So what parameters will I need to pass to ./configure if I want to
> support PTX offloading?

Pre-remark: I think that the page will be
updated, once the support has been merged to the trunk.

I think using the triplet "nvptx-unknown-none" instead of

> So if I want to have CPU, KNL and PTX, do I end up building three compilers?

That's my understanding. You then generate for the offloading/target section
code for the host (as fall back) and for one or multiple accelerators. At
invokation time, you then decide which accelerator to use (KNL, PTX or
host fallback.) Assuming that you target both accelerators during

> Finally, is the nvptx-tools project mentioned in Tobia's page aiming
> at replacing the CUDA toolchain?

Depend's what you mean by "CUDA toolchain"; the purpose of those tools is

Namely, "as" just does some reordering and "ld" reduces the number of files
by combining the PTX files. The actual 'assembler' is in the CUDA runtime

However, GCC (plus the few aux tools) replaces the compilers (nvcc etc.)
as that task is done by GCC.

>> Also, are other GPUs such as the AMD ATI and the built-in GPUs such as
>> the Intel GPU and AMD fusion supported?

There was some work underway to support OpenACC with OpenCL as output,
which is then fed to the OpenCL runtime library. The OpenACC part of
that work ended up in gomp-4_0-branch and is hence not lost. I don't
recall whether there was a branch or patch for the OpenCL support part.

For AMD's HSA, see Jakub's email.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]