Re: [easybuild] foss + CUDA toolchain

[Fotis Georgatos]

On Jan 25, 2017, at 9:57 AM, Joachim Hein  wrote:
> Do we need/want to rename goolfc or is there a severe difference between 
> goolf and foss.

This is not exact science, but most foss toolchains differ by goolf on their 
reliance 
on binutils (and in general more thorough GCC bootstrapping, modulo the 1st/2nd 
foss instances).

I’d opt for making this definition exact in, say, eb/4.x release since people 
may have good
reasons to go one way or another, therefor it is a useful feature and 
differentiation.

CUDA enabled toolchains based on GCC could follow along, in the same pattern. 
Thoughts?

F.

-- 
echo "sysadmin know better bash than english" | sed s/min/mins/ \
  | sed 's/better bash/bash better/' # signal detected in a CERN forum

Re: [easybuild] foss + CUDA toolchain

[Joachim Hein]

On 25 Jan 2017, at 07:41, Kenneth Hoste 
> wrote:



On 24/01/2017 16:56, Benjamin Evans wrote:
​Davide,

Seems like a good idea to me. Would it make sense to build it on top of  the 
gcccuda​ toolchain? Maybe call it fosscuda to fit with several of the other 
toolchains that include CUDA?

+1, it would make sense, but someone else would have to pull the effort here...

Doing this on top of gcccuda and naming it fosscuda makes sense to me (since 
'intelcuda' is already a known toolchain).



I thought that was what goolfc is meant to be.  Looking at 
http://easybuild.readthedocs.io/en/latest/eb_list_toolchains.html there seems 
no difference between goolf and foss.  So I assumed goolf is an old legacy name 
and foss the new one.  I was a bit surprised when the goolfc was named like 
that instead of fossc or fosscuda.  But then I didn’t create that toolchain and 
just went with what it there.

In the end, I documented it for the users, e.g.: 
http://lunarc-documentation.readthedocs.io/en/latest/aurora_modules/#currently-provided-toolchains

Do we need/want to rename goolfc or is there a severe difference between goolf 
and foss.  So far I assumed a proper EasyBuild standard (e.g. goolfc/2017a) 
would be agreed on now and the 2016.10 is like e.g. foss/2016.09 an 
intermediate step.

Any comments?

J.


K.

On Tue, Jan 24, 2017 at 10:41 AM, Vanzo, Davide 
> wrote:
Hello world,
I really like the idea of using foss and intel toolchain as common toolchain 
with other sites. However since we also have GPU nodes on our cluster we would 
need a foss toolchain with CUDA. I know that there is goolfc already out there 
but that does not comply to the a/b release frequency as foss does. Plus the 
fact that it is not "fossc" it does not make it obvious to users what it is.
I was then wondering if any other may benefit from such toolchain and if it 
would be a good idea starting it.

--
Davide Vanzo, PhD
Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu

Re: [easybuild] foss + CUDA toolchain

[Kenneth Hoste]

On 24/01/2017 16:56, Benjamin Evans wrote:

​Davide,

Seems like a good idea to me. Would it make sense to build it on top 
of  the gcccuda​ toolchain? Maybe call it fosscuda to fit with several 
of the other toolchains that include CUDA?


+1, it would make sense, but someone else would have to pull the effort 
here...


Doing this on top of gcccuda and naming it fosscuda makes sense to me 
(since 'intelcuda' is already a known toolchain).



K.


On Tue, Jan 24, 2017 at 10:41 AM, Vanzo, Davide 
> wrote:


Hello world,
I really like the idea of using foss and intel toolchain as common
toolchain with other sites. However since we also have GPU nodes
on our cluster we would need a foss toolchain with CUDA. I know
that there is goolfc already out there but that does not comply to
the a/b release frequency as foss does. Plus the fact that it is
not "fossc" it does not make it obvious to users what it is.
I was then wondering if any other may benefit from such
toolchain and if it would be a good idea starting it.

-- 
Davide Vanzo, PhD

Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137 
www.accre.vanderbilt.edu 

Re: [easybuild] foss + CUDA toolchain

[Benjamin Evans]

​Davide,

Seems like a good idea to me. Would it make sense to build it on top of
 the gcccuda​ toolchain? Maybe call it fosscuda to fit with several of the
other toolchains that include CUDA?

On Tue, Jan 24, 2017 at 10:41 AM, Vanzo, Davide  wrote:

> Hello world,
> I really like the idea of using foss and intel toolchain as common
> toolchain with other sites. However since we also have GPU nodes on our
> cluster we would need a foss toolchain with CUDA. I know that there is
> goolfc already out there but that does not comply to the a/b release
> frequency as foss does. Plus the fact that it is not "fossc" it does not
> make it obvious to users what it is.
> I was then wondering if any other may benefit from such toolchain and if
> it would be a good idea starting it.
>
> --
> Davide Vanzo, PhD
> Application Developer
> Adjunct Assistant Professor of Chemical and Biomolecular Engineering
> Advanced Computing Center for Research and Education (ACCRE)
> Vanderbilt University - Hill Center 201
> (615)-875-9137 <(615)%20875-9137>
> www.accre.vanderbilt.edu
>

[easybuild] foss + CUDA toolchain

[Vanzo, Davide]

Hello world,
I really like the idea of using foss and intel toolchain as common toolchain 
with other sites. However since we also have GPU nodes on our cluster we would 
need a foss toolchain with CUDA. I know that there is goolfc already out there 
but that does not comply to the a/b release frequency as foss does. Plus the 
fact that it is not "fossc" it does not make it obvious to users what it is.
I was then wondering if any other may benefit from such toolchain and if it 
would be a good idea starting it.

--
Davide Vanzo, PhD
Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu