OpenCL - What will be Microsoft's Answer?

Posted:
in macOS edited January 2014
More suckage?



OpenCL will potentially convert every mac into a mini-supercomputer by utilizing the GPU for intensive number crunching.



What will be Microsh1t's answer? Will it release parallel windows? That is, Windows OS that manages to drain all your GPU power in order to be backwards compatible with software written in 1970 and do even less than Windows Shitsta? Will it require at least 8 GB of RAM to boot up in less than 10 minutes?



Inquiring minds want to know...

Comments

  • Reply 1 of 11
    LOL it will be interesting to see, that's for sure.
  • Reply 2 of 11
    Quote:
    Originally Posted by Tauron View Post


    More suckage?



    OpenCL will potentially convert every mac into a mini-supercomputer by utilizing the GPU for intensive number crunching.



    What will be Microsh1t's answer? Will it release parallel windows? That is, Windows OS that manages to drain all your GPU power in order to be backwards compatible with software written in 1970 and do even less than Windows Shitsta? Will it require at least 8 GB of RAM to boot up in less than 10 minutes?



    Inquiring minds want to know...



    Microsoft's answer will be DirectHorseshit X Live. And it will be costly to developers. However, developers will eat it up like it's on a silver platter. It'll be used in apps and perhaps even games.



    MS has a way of tricking developers to buy shit by wrapping it up in bright colors. But when the colors begin to mix...you're left with the true color of the product: Zune-brown.
  • Reply 3 of 11
    backtomacbacktomac Posts: 4,579member
    They may just use Open CL.



    It's cross platform.



    I'm not saying that they will but that they could.
  • Reply 4 of 11
    hmurchisonhmurchison Posts: 12,423member
    http://research.microsoft.com/resear..._id=1040&0sr=a



    Quote:

    GPUs are difficult to program for general-purpose uses. Programmers can either learn graphics APIs and convert their applications to use graphics pipeline operations or they can use stream programming abstractions of GPUs. We describe Accelerator, a system that uses data parallelism to program GPUs for general-purpose uses instead. Programmers use a conventional imperative programming language and a library that provides only high-level data-parallel operations. No aspects of GPUs are exposed to programmers. The library implementation compiles the data-parallel operations on the fly to optimized GPU pixel shader code and API calls. We describe the compilation techniques used to do this. We evaluate the effectiveness of using data parallelism to program GPUs by providing results for a set of compute-intensive benchmarks. We compare the performance of Accelerator versions of the benchmarks against hand-written pixel shaders. The speeds of the Accelerator versions are typically within 50 percent of the speeds of hand-written pixel shader code. Some benchmarks significantly outperform C versions on a CPU: they are up to 18 times faster than C code running on a CPU.



    If it's not already in Microsoft's development tools it will be soon enough.
  • Reply 5 of 11
    hmurchisonhmurchison Posts: 12,423member
    Quote:
    Originally Posted by backtomac View Post


    They may just use Open CL.



    It's cross platform.



    I'm not saying that they will but that they could.



    They won't and the primary reason is



    OpenCL is meant to co-exist within an OpenGL pipeline.

    Microsoft could use OpenCL but they'd have to retrofit it to

    work within a DirecX pipeline which sounds unlikely.
  • Reply 6 of 11
    taurontauron Posts: 911member
    Quote:
    Originally Posted by kim kap sol View Post


    Microsoft's answer will be DirectHorseshit X Live. And it will be costly to developers. However, developers will eat it up like it's on a silver platter. It'll be used in apps and perhaps even games.



    MS has a way of tricking developers to buy shit by wrapping it up in bright colors. But when the colors begin to mix...you're left with the true color of the product: Zune-brown.







    No matter what they do we can rest assured that the first 20 versions will have so many bugs that each patch-fix will be larger than the previous version. In the end the patch size will grow to infinity and the whole world wide web will explode in a giant ball of fire.
  • Reply 7 of 11
    MarvinMarvin Posts: 15,322moderator
    They are developing Direct X 11 with Compute Shaders. Not sure how advanced they are for general computation but both OpenCL code and graphics shaders have limitations. The are pushing the graphics side a bit more though and have hardware tessellation, which leads to nice displacement effects. Right now, graphics use normal maps to simulate complex surfaces and they basically bend the surface normal so that the shading makes it look like the surface has more geometric detail. The silhouette and areas near the edges however are the tell-tale sign that it's fake, tessellation make things more real looking.



    This won't matter to people not doing any graphics stuff of course. Microsoft have also said that Windows 7 will support 256 CPUs so they are certainly planning for performance improvements.



    Apple are at least a year ahead of them though and I can't see their developments being as important because they don't have the same control over the hardware. Apple are moving their whole lineup to a state where GPU computation is possible including even the Macbook Air. This means that everyone with an Intel Mac that doesn't have the Radeon X1600 or Intel integrated graphics chips should see some performance boost. In some cases dramatic.
  • Reply 8 of 11
    Quote:
    Originally Posted by hmurchison View Post


    They won't and the primary reason is



    OpenCL is meant to co-exist within an OpenGL pipeline.

    Microsoft could use OpenCL but they'd have to retrofit it to

    work within a DirecX pipeline which sounds unlikely.



    Yes and No. Read the Header files listed on Khronos. They will have to write their own marriage API ala cl_gl.h, as cl_dx.h and expose their C99 compliant APIs in DirectX with OpenCL.
  • Reply 9 of 11
    hmurchisonhmurchison Posts: 12,423member
    Quote:
    Originally Posted by mdriftmeyer View Post


    Yes and No. Read the Header files listed on Khronos. They will have to write their own marriage API ala cl_gl.h, as cl_dx.h and expose their C99 compliant APIs in DirectX with OpenCL.



    Gotcha! I hadn't checked out what c99 compliancy offered. I do wonder if MSFT will just roll their own or support OpenCL or both.
  • Reply 10 of 11
    MarvinMarvin Posts: 15,322moderator
    Quote:
    Originally Posted by hmurchison View Post


    Gotcha! I hadn't checked out what c99 compliancy offered. I do wonder if MSFT will just roll their own or support OpenCL or both.



    Perhaps the GPU makers will offer an SDK like they do for CUDA and the Stream SDK or some 3rd party developer can make one. It's probably better they do it so that it gets done properly and developers don't turn to DirectX if Microsoft cripple the OpenCL implementation.
  • Reply 11 of 11
    Quote:
    Originally Posted by Marvin View Post


    Perhaps the GPU makers will offer an SDK like they do for CUDA and the Stream SDK or some 3rd party developer can make one. It's probably better they do it so that it gets done properly and developers don't turn to DirectX if Microsoft cripple the OpenCL implementation.



    They already do.



    Now that the technobabble is over perhaps we can get back to the business of trashing Microsoft?
Sign In or Register to comment.