I have just read the updated manual:
https://gcc.gnu.org/wiki/Offloading
It says to build an accel compiler, one need to:
./configure --build=x86_64-intelmicemul-linux-gnu
--host=x86_64-intelmicemul-linux-gnu
--target=x86_64-intelmicemul-linux-gnu
--enable-as-accelerator-for=x86_64-pc-linux-gnu
Oh sorry. I just checked out the svn again, and see it already
merged. Well done!
On Tue, Jan 20, 2015 at 11:59 PM, Mark Farnell wrote:
> I know that we are already in stage 4, but features such as OpenACC
> 2.0, nvptx and KNL (xeon phi) offloading support are so important
>
I know that we are already in stage 4, but features such as OpenACC
2.0, nvptx and KNL (xeon phi) offloading support are so important
for GCC, and if they have to be deferred to GCC 6.0, then it would be
a great loss to GCC, as OpenACC 2.0 makes heterogeneous manycore
programming so much easie
OpenACC 2.0 from reaching the
trunk? And does the GCC core team intend to include OpenACC 2.0 as a
feature of GCC 5.0?
On Fri, Jan 9, 2015 at 9:04 AM, Mark Farnell wrote:
> Currently, OpenACC 2.0 is in gomp-4_0-branch, but this email:
>
> https://gcc.gnu.org/ml/gcc/2015-01/msg00032.html
p-4.0_branch need to
approach the gcc release team *immediately* and explain why openacc is
essential for gcc 5, and why openacc is ready to merge into the trunk.
We need timely intervention from the gcc release team to ensure
openacc makes it to gcc 5
On Fri, Jan 9, 2015 at 10:09 PM, Tobias Burnus
wrote:
Currently, OpenACC 2.0 is in gomp-4_0-branch, but this email:
https://gcc.gnu.org/ml/gcc/2015-01/msg00032.html
says that gcc 5.0 will enter stage 4 on Friday 16th January, and from
that point onward, only bug fixing patches will be accepted.
So will gomp-4_0-branch be able to be merged into the
>From the svn log, I saw tschwinge did a lot of bug fixing on the
gomp-4_0-branch, and recently merged trunk to gomp-4_0-branch without
mention of any outstanding conflicts. Does this signify an imminent
merge of the gomp-4_0-branch to the trunk?
If so, I am really excited to try out openacc
Als
As in the offloading documentation at gcc.gnu.org, currently one must
run ./configure and make for each accelerator and the host itself.
This is very inconvenient and prone to error.
Would it be possible to change the configure script so that all the
user needs to do is to:
* specify the target ho
obias Burnus
wrote:
> 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 https://gcc.gnu.org/wiki/Offloading page will be
> updated, once the support has been merged to the
the nvptx-tools project mentioned in Tobia's page aiming
at replacing the CUDA toolchain?
Thanks!
Mark
On Wed, Dec 17, 2014 at 9:05 AM, Jakub Jelinek wrote:
> On Wed, Dec 17, 2014 at 08:54:06AM +1300, Mark Farnell wrote:
>> That's good news. Does it mean that if I want
usion supported? If so, are they already
supported in the trunk, or only specific branch?
Finally, when will support of Knights Corner (knc) be added to the
trunk and/or one of the branches?
Thanks!
Mark
On Tue, Dec 16, 2014 at 9:22 PM, Tobias Burnus
wrote:
> Mark Farnell wrote:
>> H
Hi,
Has OpenACC 2.0 support been merged into the trunk yet? If not, then
is it contained in gomp-4_0-branch?
If so, what parameters should I pass to ./configure to enable OpenACC
2.0, and relevant backends such as CUDA, MIC and other GPGPU/manycore
architecture?
Also, I have a feeling that Open
12 matches
Mail list logo
