-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[gui] Force GGUI to go through host memory (nuking interops) #7218
Conversation
✅ Deploy Preview for docsite-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
dde614c
to
960e93c
Compare
4521243
to
8fa7db0
Compare
nit: Do you plan to break this PR down? |
I will put all the RHI changes / bug fixes in their own PR, and then the GGUI changes kind of have to be a big blob to pass all tests. I think that change set would be around +750 lines. I can seperate them through ghstack perhaps but individual ones won't pass CI. |
Related: #7218 Without this GGUI will mess with the OpenGL backend because both tries to initialize & destroy GLFW. There is an issue tho with dependency. Which target should `rhi/window_system` belong to? Maybe we need a device API target that collects all the specific backends and generate a static lib with all backends and optional dependencies like GLFW? (Anyways, that will be a TODO for another PR) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
59af181
to
ef5c547
Compare
7496337
to
c890284
Compare
eb839a2
to
f39bdef
Compare
6f6a02d
to
de65271
Compare
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.
lgtm, @ailzhang and @AmesingFlank might wanna double check this huge pr.
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.
Thanks!
Related: taichi-dev#7218 Without this GGUI will mess with the OpenGL backend because both tries to initialize & destroy GLFW. There is an issue tho with dependency. Which target should `rhi/window_system` belong to? Maybe we need a device API target that collects all the specific backends and generate a static lib with all backends and optional dependencies like GLFW? (Anyways, that will be a TODO for another PR) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
…#7234) Part of taichi-dev#7218 Related (ndarray meta-programming): taichi-dev#7231 I would certainly like to share this code between the field vesion and NDArray version Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
…dev#7218) Issue: # Contains: - [x] taichi-dev#7230 - [x] taichi-dev#7232 - [x] taichi-dev#7233 - [x] taichi-dev#7234 Merge those before this PR (to reduce the size of the change set) ### Brief Summary Nuking all interops, in order to reduce code complexity of GGUI & provide path ways to other rendering frontends (e.g. metal) --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Issue: #
Contains:
Merge those before this PR (to reduce the size of the change set)
Brief Summary
Nuking all interops, in order to reduce code complexity of GGUI & provide path ways to other rendering frontends (e.g. metal)