Hi all,
I'm happy to announce that the dcompute modifications to LDC are
now in the master branch of LDC. The dcompute extensions require
LLVM 3.9.1 or greater for NVPTX/CUDA and my fork[1] of LLVM for
SPIRV.
Someone (sorry I've forgotten who!) at dconf said they'd make a
docker image of th
On 29/05/2017 10:33 AM, Nicholas Wilson wrote:
Hi all,
I'm happy to announce that the dcompute modifications to LDC are now in
the master branch of LDC. The dcompute extensions require LLVM 3.9.1 or
greater for NVPTX/CUDA and my fork[1] of LLVM for SPIRV.
Someone (sorry I've forgotten who!)
On Monday, 29 May 2017 at 09:39:53 UTC, rikki cattermole wrote:
On 29/05/2017 10:33 AM, Nicholas Wilson wrote:
Hi all,
I'm happy to announce that the dcompute modifications to LDC
are now in the master branch of LDC. The dcompute extensions
require LLVM 3.9.1 or greater for NVPTX/CUDA and my
On 29/05/2017 10:52 AM, Nicholas Wilson wrote:
On Monday, 29 May 2017 at 09:39:53 UTC, rikki cattermole wrote:
On 29/05/2017 10:33 AM, Nicholas Wilson wrote:
Hi all,
I'm happy to announce that the dcompute modifications to LDC are now
in the master branch of LDC. The dcompute extensions requi
On 5/29/2017 2:33 AM, Nicholas Wilson wrote:
Hi all,
I'm happy to announce that the dcompute modifications to LDC are now in the
master branch of LDC. The dcompute extensions require LLVM 3.9.1 or greater for
NVPTX/CUDA and my fork[1] of LLVM for SPIRV.
Someone (sorry I've forgotten who!) at
Hi Ali,
The book is great ( got it recently ) but there are some things
that may make be better.
I found the book a bit unwieldy ( hardcover ) version. With its
700+ pages, its kind of hard to take anywhere. When i take it to
work and back home, its like carrying a brick with me :)
Another
On Monday, 29 May 2017 at 20:36:26 UTC, Walter Bright wrote:
On 5/29/2017 2:33 AM, Nicholas Wilson wrote:
Hi all,
I'm happy to announce that the dcompute modifications to LDC
are now in the master branch of LDC. The dcompute extensions
require LLVM 3.9.1 or greater for NVPTX/CUDA and my fork[
On 05/29/2017 03:06 PM, Wulfklaue wrote:
> The book is great ( got it recently ) but there are some things that may
> make be better.
Thank you for your feedback. :)
> 87 in memory management the
> experimental unsafe memory management is not written about.
Yes, there are things I would like t
On 5/29/2017 3:52 PM, Nicholas Wilson wrote:
How about calling it D-GPU ? I bet you'd get a lot more clicks on a name like
that.
Thanks, I called it dcompute because naming things is right up there with cache
invalidation.
Calling it D-GPU would be misleading because there should be no reason
On Tuesday, 30 May 2017 at 00:12:51 UTC, Walter Bright wrote:
On 5/29/2017 3:52 PM, Nicholas Wilson wrote:
How about calling it D-GPU ? I bet you'd get a lot more
clicks on a name like that.
Thanks, I called it dcompute because naming things is right up
there with cache invalidation.
Calling
On 5/29/2017 6:10 PM, Nicholas Wilson wrote:
there are also GitHub topics [1] which I will also properly fill out. I just
done a pass over the README.md
[1]: https://github.com/blog/2309-introducing-topics
Good. Making the content google-friendly is also extremely important. Back in
the earl
On Tuesday, 30 May 2017 at 02:46:12 UTC, Walter Bright wrote:
On 5/29/2017 6:10 PM, Nicholas Wilson wrote:
there are also GitHub topics [1] which I will also properly
fill out. I just done a pass over the README.md
[1]: https://github.com/blog/2309-introducing-topics
Good. Making the content
On Monday, 29 May 2017 at 20:36:26 UTC, Walter Bright wrote:
May I suggest, however, that the name DCompute is a bit
generic, and provides no hint that it provides GPU programming
for D.
How about calling it D-GPU ? I bet you'd get a lot more clicks
on a name like that.
For what it's wort
13 matches
Mail list logo
