-
Notifications
You must be signed in to change notification settings - Fork 543
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
Add RenderDoc API integration in the Vulkan backend #52
Comments
copybara-service bot
pushed a commit
that referenced
this issue
Feb 7, 2020
Progress on #52. We can use RenderDoc without integrating with its API through `vulkan_inference_gui`, but not through `iree-run-mlir`. We need to explicitly start/stop capture through the API when only using Vulkan compute (no graphics). This PR imports the API header file so we can use it in future change. Includes are of the format (tested with Bazel and CMake): ``` #include "third_party/renderdoc_api/app/renderdoc_app.h" ``` Closes #696 PiperOrigin-RevId: 293834602
ScottTodd
added a commit
to ScottTodd/iree
that referenced
this issue
Feb 7, 2020
Surface level progress on iree-org#52 that lets us record captures from `iree-run-mlir` (with the latest nightly build of RenderDoc).
ScottTodd
added a commit
to ScottTodd/iree
that referenced
this issue
Feb 7, 2020
Surface level progress on iree-org#52 that lets us record captures from `iree-run-mlir` (with the latest nightly build of RenderDoc).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RenderDoc provides a rich API by which we can trigger capture and demarcate "frames" (probably just top-level invocations). We can add comments to frames that show in the UI which would make it easier to map back to original invocations. RenderDoc can also capture stack traces on calling into the Vulkan API entry points which would be useful when using the sequencer codegen (otherwise we'd just see VM stacks).
The text was updated successfully, but these errors were encountered: