Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support switching burn-wgpu between WebGPU implementations (wgpu <-> Dawn) #1583

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Commits on May 9, 2024

  1. burn-wgpu: Move any use of wgpu into a separate module

    Currently the burn-wgpu crate is hardcoded to use the wgpu WebGPU
    implementaion. It would be nice to be able to use other WebGPU
    implementations as new features may land at different times, and there
    may be potential performance gains to unlock. So, separate any use of
    the wgpu crate into a separate module, in preparation for adding the
    ability to target other WebGPU implementaions.
    
    Signed-off-by: Piotr Stankiewicz <piotr.stankiewicz@docker.com>
    p1-0tr committed May 9, 2024
    Configuration menu
    Copy the full SHA
    2e060dc View commit details
    Browse the repository at this point in the history

Commits on May 13, 2024

  1. burn-wgpu: Allow using Dawn instead of/along wgpu

    Dawn, Google's WebGPU impelementation, currently supports feattures
    which wgpu does not. For example using 16 bit floats in shaders. So, add
    the ability to build the burn-wgpu backend against Dawn.
    
    Signed-off-by: Piotr Stankiewicz <piotr.stankiewicz@docker.com>
    p1-0tr committed May 13, 2024
    Configuration menu
    Copy the full SHA
    3212b1a View commit details
    Browse the repository at this point in the history