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

Don't require Halide_WebGPU when using wasm (#8063) #8065

Merged
merged 2 commits into from
Feb 6, 2024

Conversation

steven-johnson
Copy link
Contributor

No description provided.

@steven-johnson steven-johnson merged commit 665804c into main Feb 6, 2024
16 checks passed
@steven-johnson steven-johnson deleted the srj/Halide_WebGPU branch February 6, 2024 23:34
steven-johnson added a commit that referenced this pull request Feb 19, 2024
* Don't require Halide_WebGPU when using wasm (#8063)

* trigger buildbots
steven-johnson added a commit that referenced this pull request Feb 19, 2024
…elease (#8106)

* Don't require Halide_WebGPU when using wasm (#8063) (#8065)

* Don't require Halide_WebGPU when using wasm (#8063)

* trigger buildbots

* [WebGPU] Update to latest native headers (#8081)

* [WebGPU] Update to latest native headers

* Remove #ifdef for `requiredFeature[s]Count`

* Pass nullptr to wgpuCreateInstance
  * Emscripten currently requires this
  * Dawn accepts it too

* Use nullptr for another wgpuCreateInstance call

---------

Co-authored-by: James Price <jrprice@google.com>
ardier pushed a commit to ardier/Halide-mutation that referenced this pull request Mar 3, 2024
* Don't require Halide_WebGPU when using wasm (halide#8063)

* trigger buildbots
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants