Live data from Hacker News

Viewing profile — hjabird

hjabird

HN member
Joined
Thu, Dec 14, 2023, 8:23 PM UTC
HN karma
104
Public activity
12 items

About hjabird

No profile information was provided.

Recent public activity

  1. comment
    Comment #39346971

    There are some great replies to my comment - my original comment was too reductive. However, I still think that entrenching CUDA as the de-facto language for heterogeneous computin…

  2. comment
    Comment #39346686

    True. This is the big advantage of an open standard instead jumping from one vendors walled garden to another.

  3. comment
    Comment #39345853

    The problem with effectively supporting CUDA is that encourages CUDA adoption all the more strongly. Meanwhile, AMD will always be playing catch-up, forever having to patch issues,…

  4. comment
    Comment #38938756

    Intel's modern compilers (icx, icpx) are clang-based. There is an open-source version [1], and the closed-source version is built atop of this with extra closed-source special sauc…

  5. comment
    Comment #38938551

    What kind of performance is achieveable with some of the features that Vcc enables (true function calls, function pointers, goto), and what are some of the limitations? On GPU, fun…

  6. comment
    Comment #38727306

    I wouldn't expect them to drop CUDA support, even if SYCL is a viable alternative: * The CUDA backend is mature, featureful, and significant effort has been invested into optimisin…

  7. comment
    Comment #38707122

    A challenge with this is that all current AMD GPU support in SYCL compilers (DPC++ w/ Codeplay's oneAPI for AMD GPUs, and AdaptiveCpp), is built atop of ROCm / HIP. If AMD were to …

  8. comment
    Comment #38707079

    > The performance of any application on SYCL is currently quite poor. SYCL can get pretty much equivalent performance in Kernels to eg. CUDA. Try looking at SYCL performance papers…

  9. comment
    Comment #38695439

    SYCL (closely related to oneAPI) isn't single-vendor-controlled. It's a Khronos open standard. If you take a look at the spec, you'll see contributions from various universities, Q…

  10. comment
    Comment #38695297

    > Why would you want OpenCL? OpenCL is stricter with the results of floating point operations, and makes different assumptions with respect to memory aliasing. Whether or not this …

  11. comment
    Comment #38647073

    SYCL isn't based on OpenCL. SYCL (SYCL-2020 spec) supports multiple backends, including Nvidia's CUDA, AMD's HIP, OpenCL, Intel's Level-zero, and also running on the host CPU. This…

  12. comment
    Comment #38646931

    SYCL is gaining traction, especially in the HPC community since it can target AMD, Nvidia and Intel hardware with one codebase. A fun fact is the GROMACS (a major application for m…