Seriously? Wha.. what? Someone needs to get help.
And it wasn't me. I am a member of the People's Front of Julia.
(contrived Python reference intentional)
On Wed, 8 May 2019 at 22:57, Jeffrey Layton wrote:
> I wrote some OpenACC articles for HPC Admin Magazine. A number of
> pro-OpenMP people a
I wrote some OpenACC articles for HPC Admin Magazine. A number of
pro-OpenMP people attacked me on twitter (you know, OpenACC sucks, OpenMP
is great). I received a private email threatening to kill me and my family
if I didn't stop writing about OpenACC. Given your pro-OpenMP, anti-OpenACC
stance,
Huh ... ?? Weird, scary ...
Just MHO. Dropping off this thread now ...
rbw
Sent from my iPhone
> On May 8, 2019, at 4:29 PM, Jeffrey Layton wrote:
>
> I was just pointing out that gcc has Open ACC capability on AMD GPUs.
>
> I didn't realize you part of the OpenMP Nazis. Were you the one
I was just pointing out that gcc has Open ACC capability on AMD GPUs.
I didn't realize you part of the OpenMP Nazis. Were you the one that
threatened me and my family because I wrote about OpenACC?
On Wed, May 8, 2019, 15:48 Richard Walsh wrote:
>
> Jeffry/All,
>
> Yes ... but given the choic
Hi all,
I have a small pile of Dell sliding rack rails from departed servers
(and no current Dell rack mounted equipment). Each rail has 3 slots
into which pegs on the side of the server drop. There are two types of
slot spacings. The back two slots are in the same in all rails, but the
fr
On 5/8/19 3:55 PM, Ryan Novosielski wrote:
On May 8, 2019, at 2:42 PM, Michael Di Domenico wrote:
On Wed, May 8, 2019 at 2:14 PM Gus Correa wrote:
Once upon a time portability, interoperabiilty, standardization, were
considered good software and hardware attributes.
Whatever happened to the
Is NVIDIA really the only one to blame? Intel was very reluctant to support
open SPMD languages (even their own ISPC), which would have delivered
better performance across the whole ecosystem, to deny GPUs a foothold.
On Wed, May 8, 2019 at 4:56 PM Ryan Novosielski
wrote:
> > On May 8, 2019, at
> On May 8, 2019, at 2:42 PM, Michael Di Domenico
> wrote:
>
> On Wed, May 8, 2019 at 2:14 PM Gus Correa wrote:
>>
>> Once upon a time portability, interoperabiilty, standardization, were
>> considered good software and hardware attributes.
>> Whatever happened to them?
>
> millennials?
Tha
Jeffry/All,
Yes ... but given the choice of using OpenACC or OpenMP (if you are not going
to write CUDA-HIP code for that extra 10% of performance) which captures most
(all?) of the features of OpenACC, is a standard likely to outlive OpenACC, and
should run on any vendor’s accelerators, incl
Don't forget that gcc supports both NV and AMD GPUs with OpenACC. That's
one of the lead compilers listed on the Frontier specs.
Jeff
On Wed, May 8, 2019 at 3:29 PM Richard Walsh wrote:
>
> All,
>
> Cray has deprecated support for in OpenACC in light of the OpenMP 4.5 and
> 5.0 standards, and
All,
Cray has deprecated support for in OpenACC in light of the OpenMP 4.5 and 5.0
standards, and their target and data directives. NVIDIA’s PGI Compiler group
will keep OpenACC going for a while, but on AMD devices ... maybe not. That
Cray will support only OpenMP on Frontier seems to be a l
On 5/8/19 10:47 AM, Jörg Saßmannshausen wrote:
As I follow these things rather loosely, my understanding was that OpenACC
should run on both nVidia and other GPUs. So maybe that is the reason why it
is a 'pure' AMD cluster where both GPUs and CPUs are from the same supplier?
IF all of that is wo
On 5/8/19 2:42 PM, Michael Di Domenico wrote:
On Wed, May 8, 2019 at 2:14 PM Gus Correa wrote:
Once upon a time portability, interoperabiilty, standardization, were
considered good software and hardware attributes.
Whatever happened to them?
millennials?
They seem to ruin everything, don't
On 5/8/19 2:13 PM, Gus Correa wrote:
On Wed, May 8, 2019 at 1:47 PM Jörg Saßmannshausen
mailto:sassy-w...@sassy.formativ.net>>
wrote:
Dear all,
I think the answer to the question lies here:
https://en.wikipedia.org/wiki/OpenACC
As I follow these things rather loosely, my
I disagree. IT is a cyclical industry.
Back in the bad old days codes were written to run on IBM mainframes. Which
used the ECDIC character set.
There were Little Endian and Big Endian machines.
VAX machines had a rich set of file IO patterns. I really dont think you
could read data written on an I
On Wed, May 8, 2019 at 2:14 PM Gus Correa wrote:
>
> Once upon a time portability, interoperabiilty, standardization, were
> considered good software and hardware attributes.
> Whatever happened to them?
millennials?
___
Beowulf mailing list, Beowulf@b
On Wed, May 8, 2019 at 1:47 PM Jörg Saßmannshausen <
sassy-w...@sassy.formativ.net> wrote:
> Dear all,
>
> I think the answer to the question lies here:
>
> https://en.wikipedia.org/wiki/OpenACC
>
> As I follow these things rather loosely, my understanding was that OpenACC
> should run on both nVi
Dear all,
I think the answer to the question lies here:
https://en.wikipedia.org/wiki/OpenACC
As I follow these things rather loosely, my understanding was that OpenACC
should run on both nVidia and other GPUs. So maybe that is the reason why it
is a 'pure' AMD cluster where both GPUs and CPUs
All,
I think the comparison with RoadRunner is off. Any application that
already has
a CUDA version can be largely converted to run on AMD GPUs with a perl
script
with some minor adjustments. Those without GPU implementations will have
to
be converted (many are already having this done under E
On 5/7/19 6:14 PM, Lux, Jim (337K) wrote:
On 5/7/19, 2:00 PM, "Beowulf on behalf of Prentice Bisbal via Beowulf"
wrote:
> I think it is interesting that they are using AMD for
> both the CPUs and GPUs
I agree. That means a LOT of codes will have to be ported from CUDA
On Wed, 8 May 2019 06:54:38 +1000
Lance Wilson via Beowulf wrote:
Hi @ all,
> The other community that will struggle is AI/ML as they are pushing
> very hard into the CUDA space.
yes, however
https://rocm.github.io/tensorflow.html
There are some benchmarks out there which look very promising.
21 matches
Mail list logo
