Re:Llvmpipe: The Jitted OpenGL software renderer inside Mesa
by AshleysBrain on Monday January 11, 2016 @02:31PM
(#10882658)
This looks interesting. I wonder if browsers could implement this as a fallback for WebGL when the drivers are missing or blacklisted? Chrome on Windows uses SwiftShader to fallback to software-rendered WebGL, and I think IE11/Edge use WARP, a DX11 software renderer. Firefox and other browsers on non-Windows platforms could benefit. But by the sound of it running this against the WebGL conformance tests could be spotty!
[ Parent
| on HN ]
Re:Llvmpipe: The Jitted OpenGL software renderer inside Mesa
by yoklov on Tuesday January 12, 2016 @09:16AM
(#10887493)
Does Chrome still use SwiftShader? I've tried on a reasonably large number of machines to verify this, with no luck. Including machines that have blacklisted GPUs.
It's clear that there seems to be some cases where it kicks in (or at least theres some legacy cruft that references it if not) but hell if I've ever seen it happen.