home.social

#spir — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #spir, aggregated by home.social.

fetched live
  1. @cykeltutten
    En #cykel er en frihedsmaskine, og alle fortjener #frihed: både #mennesker og #svin. ☮️

    Køb derfor #vegansk #hotdog i stedet for dem der er lavet af #grise, der er blevet indespærret, kvalt i et CO₂ #gaskammer, hakket i stykker, og til allersidst stoppet op i deres egen røv. 🐽 veganism.social/@veganguide/11

    #Spir #pølser fra #Netto er ikke dyrere end dem med #dyremishandling. 🌭

  2. Early Bird pricing for the Shading Language Symposium ends on January 18th. Register now to attend this inaugural, ground-breaking event that will bring together graphics and computer shader programmers, researchers and technical artists with shading language implementers to explore the landscape of shading languages, their future development, and new techniques.

    khronos.org/events/shading-lan
    -V

  3. Khronos Group Welcomes Lisuan Technology as Contributor Member

    Lisuan Technology is a company dedicated to the research and development of graphics rendering GPUs. Founded by leading figures in the GPU industry, it possesses capabilities in large-scale chip R&D, top-level architecture design, software stack design, and mass production. They are interested in , , , , , , and .
    lisuantech.com/

  4. Khronos' OpenCL Working Group has issued a Request for Proposal (#RFP) for OpenCL LLVM SPIR-V Backend. The goal of this project is to address and integrate specific functionalities that are currently available in the translator project but missing from the backend. All bids are due December 6, 2024.

    Learn more: khronos.org/rfp/khronos-opencl

  5. Once @microsoft 's Shader Model 7 is released, 12 will accept shaders compiled to SPIR-V. Microsoft is working with the Khronos and Working Groups to ensure that this transition benefits the whole development ecosystem.

    devblogs.microsoft.com/directx

  6. Was looking into #WGSL this weekend and keeps me wondering why I should learn a new shading language. What does it exactly solve? Think will keep to #spir-v toolset for now using #HLSL . If I need to learn something new , best that it is a standard I can use for most of my projects.

  7. I should mention that this isn't just a matter of the dominant player intentionally boycotting standards that would make them lose the vendor lock-in advantage (hello #NVIDIA). All major vendors are guilty of this one way or the other. For example, #AMD unjustifiably pulled (or maybe failed to add) #SPIR and #CPU support from their new #OpenCL implementation. #Intel's #oneAPI (even while still leveraging the OpenCL backend) effectively failed on any other OpenCL platform.

  8. @halcy
    Former SPIR WG chair here.
    It's "spear vee"

    Mike Houston proposed the original SPIR at the January 2011 Khronos F2F. He gave it the name, expanded the acronym *and* was explicit about the pronunciation as "spear".

    SPIR-V came later. Khronos has always pronounced it "spear vee"

    That said, language is a living thing, so use what you like.

    #spirv #spir