-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Roll Emdawnwebgpu and repoint USE_WEBGPU tests at Emdawnwebgpu #25397
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
base: main
Are you sure you want to change the base?
Conversation
In preparation to remove USE_WEBGPU entirely (emscripten-core#24265). Ideally these tests would live in Dawn, but we don't have a way to automate tests in the browser yet, so for the moment we'll keep them in Emscripten. DO NOT SUBMIT: Needs Emdawnwebgpu roll in order to pass
@lokokung PTAL |
a88588a
to
ffb124d
Compare
ffb124d
to
d12517b
Compare
3b2d73d
to
4c7bf8a
Compare
4c7bf8a
to
4f93d5f
Compare
|
||
def test_webgpu_get_device_pthreads(self): | ||
self.btest_exit('webgpu_get_device.cpp', cflags=['-Wno-error=deprecated', '-sUSE_WEBGPU', '-pthread']) | ||
self.set_setting('NO_DEFAULT_TO_CXX', 0) # emdawnwebgpu uses C++ internally |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What to do about this long term?
Is this some fundamental difference between the old and new implementation? The only one manged to avoid depending on libc++ library functions but the new one did not? Are folks who use this library simply bound to link with C++?
raise Exception('Remote ports require Emscripten 4.0.10+.') | ||
|
||
|
||
def clear(ports, settings, shared): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can / should we update the port as a separate PR that we can land first?
In preparation to remove USE_WEBGPU entirely (#24265). Ideally these tests would live in Dawn, but we don't have a way to automate tests in the browser yet, so for the moment we'll keep them in Emscripten.