Skip to main content

Gpu tagged news

The Khronos Group today announces the creation of the Vulkan Safety Critical Working Group, to enable safety critical industries to take advantage of advancements in GPU graphics and compute acceleration, and display control, at the highest levels of safety integrity. Safety critical graphics are a key component for industries such as automotive, avionics, medical and energy. As display requirements become more advanced, safety critical graphics APIs must evolve to meet the industries’ needs. Now, automotive and other industries are seeking advanced GPU graphics, compute and display functionality that can be deployed in safety critical systems. In response to this industry demand, this new Khronos Working Group will create open, royalty-free API standards based on the existing Vulkan API specification to enable safety critical industries to utilize advanced graphics and compute acceleration. To best suit these market’s needs, the new API will aim to be compatible with industry standards for safety critical software, such as RTCA DO-178C Level A / EASA ED-12C Level A (avionics); FACE (Future Airborne Capability Environment) (avionics); and ISO 26262 ASIL D (automotive).

Fifth-year student Adam Kelly focused on finding the most efficient way possible to simulate quantum computing. Adam’s project QCGPU is a high performance, hardware accelerated quantum computer simulator written with Python and OpenCL. News coverage and short interview with Adam are online, as well as the research paper. Congratulations Adam!

The Khronos Group OpenCL API is a SIMD programming model which maps well to the GPU but mostly bypass the fixed graphics-specific logic. The latest Radeon GPU Profiler 1.4 (RGP) now has the ability to profile OpenCL workloads in RGP. Most of the major RGP features that you’re used to using for profiling graphics workloads generated by Vulkan and DirectX 12 are there when profiling OpenCL applications, including the workload and barrier overviews.

NVIDIA has released the new VRWorks Graphics SDK V3.0 for application and headset developers along with the NVIDIA display driver 411.63, both updated for NVIDIA’s new Turing GPU generation. The drivers are available for download and the SDK has been posted. The SDK includes an OpenGL sample to demonstrate Turing’s “Variable Rate Shading” (VRS) feature showing how to vary fragment load across the screen, e.g. for foveated rendering. Another sample demonstrates Turing’s “Multi-View Rendering” (MVR) feature by showing how to render the same scene from different viewpoints. There are Vulkan versions of the samples too.

Recent work from Boston University has shown that with key optimizations that leverage OpenCL on Arria 10 FPGAs for 3D fast fourier transforms (FFTs), a common HPC workload, the performance can beat out FFT specific IP cores as well as GPU and CPU implementations of the same problem.

The OpenCL support by NNVM & TVM session from Linaro Connect 2018 in Hong Kong is now online. Abstract: To use mobile GPU to accelerate deep learning inference on ARM platforms in device side, OpenCL support seems a proper and promising fit. NNVM is an open compiler for AI frameworks with graph IR implementation, and TVM is an open source end-to-end Tensor IR/DSL stack. NNVM together with TVM provides a flexible architecture to support different frameworks and backends. OpenCL is one of the supported backends by NNVM & TVM now, the latest status and some how-tos will be discussed in this session.

AMD is announcing the release of V-EZ, a middleware layer that significantly reduces the house-keeping overhead of Vulkan making it easier to use and more accessible to a broader base of developers. V-EZ will still retain the most powerful capabilities of Vulkan but with a simplified API that can be mixed with standard Vulkan where needed. Read on to learn more about some of V-EZ’s key technical features.

Apple announced several updates to the Mac lineup earlier this month at WWDC. Geekbench 4, which includes a new GPU Compute Benchmark that measures the performance of GPUs at performing compute tasks, shows that GPU performance with OpenCL has improved considerably with an increase of up to 80% when compared to the equivalent 2015 model. If you’re interested in how your computer compares you can download Geekbench 4. Find the complete benchmark results on the Geekbench website.

The GPU Technology Conference (GTC2017) will be running from May 8-11 this year in San Jose Convention Center. This year will see many sessions related to Khronos Technology including OpenCL, OpenGL, OpenVX, Vulkan and WebGL. NVIDIA has just added more sessions to their schedule. Check a list of Khronos related sessions on the Khronos site, or visit the NVIDIA GTC site to see all sessions.

The GPU Technology Conference (GTC2017) will be running from May 8-11 this year in San Jose Convention Center. This year will see many sessions related to Khronos Technology including OpenCL, OpenGL, OpenVX, Vulkan and WebGL. Check a list of Khronos technology only sessions on the Khronos site, or visit the NVIDIA GTC site to see all sessions.

At GDC 2017, in San Francisco during February, Khronos™ released several new Vulkan® extensions for cross-platform Virtual Reality rendering and multiple GPU access. This functionality has been initially released as KHX extensions to enable feedback from the developer community before being incorporated into final specifications. One key question that we have been asked since GDC is whether the Vulkan multi-GPU functionality is specifically tied to ship only on Windows 10.

Furian is designed to address the increasing compute requirements across multiple applications and market segments with efficient use of compute APIs including OpenCL 2.0, Vulkan 1.0 and OpenVX 1.1*. Furian adds a bi-directional GPU/CPU coherent interface for efficient sharing of data; and a transition to user mode queues from kernel mode queues which reduces latency and CPU utilization for compute operations. Based on a published Khronos specification, GPUs based on the PowerVR Furian architecture are expected to pass the Khronos Conformance Testing Process. Current conformance status can be found at