You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update on "[ET-VK] Move files using the Vulkan API to vk_api/"
and move from namespace `api` to `vkapi`. This gave me a major headache in the number of places to update.
This stack orgnaizes ET-VK neatly into three abstraction levels, both by folder and by namespace:
1. `namespace vkcompute` and `graph/`: for operator computation implementation and scheduling.
2. `namespace vkcompute::api` and `graph/api/`: for tensor objects (and other objects wrapping our VulkanBuffer/VulkanImage).
3. `namespace vkcompute::vkapi` and `graph/api/vk_api/`: for direct users of Vulkan API
Additionally, we have
- `namespace vkcompute::utils` and `graph/api/utils/`: for utils used by both namespace `api` and `vkapi`
Differential Revision: [D59281539](https://our.internmc.facebook.com/intern/diff/D59281539/)
[ghstack-poisoned]
description: Create a report to help us reproduce and fix the bug
3
+
4
+
body:
5
+
- type: markdown
6
+
attributes:
7
+
value: >
8
+
#### Before submitting a bug, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/pytorch/executorch/issues?q=is%3Aissue+sort%3Acreated-desc+).
9
+
- type: textarea
10
+
attributes:
11
+
label: 🐛 Describe the bug
12
+
description: |
13
+
Please provide a clear and concise description of what the bug is.
14
+
15
+
If relevant, add a minimal example so that we can reproduce the error by running the code.
16
+
17
+
If the code is too long (hopefully, it isn't), feel free to put it in a public gist and link it in the issue: https://gist.github.com.
18
+
19
+
Please also paste or describe the results you observe instead of the expected results. If you observe an error, please paste the error message including the **full** traceback of the exception. It may be relevant to wrap error messages in ```` ```triple quotes blocks``` ````.
20
+
placeholder: |
21
+
A clear and concise description of what the bug is.
22
+
23
+
```python
24
+
# Sample code to reproduce the problem
25
+
```
26
+
27
+
```
28
+
The error message you got, with the full traceback.
29
+
```
30
+
validations:
31
+
required: true
32
+
- type: textarea
33
+
attributes:
34
+
label: Versions
35
+
description: |
36
+
Please run the following and paste the output below.
description: Submit a proposal/request for a new ExecuTorch feature
3
+
4
+
body:
5
+
- type: textarea
6
+
attributes:
7
+
label: 🚀 The feature, motivation and pitch
8
+
description: >
9
+
A clear and concise description of the feature proposal. Please outline the motivation for the proposal. Is your feature request related to a specific problem? e.g., *"I'm working on X and would like Y to be possible"*. If this is related to another GitHub issue, please link here too.
10
+
validations:
11
+
required: true
12
+
- type: textarea
13
+
attributes:
14
+
label: Alternatives
15
+
description: >
16
+
A description of any alternative solutions or features you've considered, if any.
17
+
- type: textarea
18
+
attributes:
19
+
label: Additional context
20
+
description: >
21
+
Add any other context or screenshots about the feature request.
0 commit comments