The operator 'aten::upsample_nearest1d.out' is not currently supported on the DML backend and will fall back to run on the CPU
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- machine-learning
Research direction
Reproduce the warning from torch.nn.functional.py at the reported upsample_nearest1d call, then inspect torch_directml/csrc/dml/dml_cpu_fallback.cpp around line 17 and the operator-support implementation. Done means aten::upsample_nearest1d.out executes on the DML backend without a CPU fallback, with coverage confirming the behavior.
Written by the indexing model from the issue text.
Description
When I use the directml on amd platform,i got the warning ,and it fall back to run on CPU。
C:\Users\amd.conda\envs\aippt\Lib\site-packages\torch\nn\functional.py:4048: UserWarning: The operator 'aten::upsample_nearest1d.out' is not currently supported on the DML backend and will fall back to run on the CPU. This may have performance implications. (Triggered internally at C:__w\1\s\pytorch-directml-plugin\torch_directml\csrc\dml\dml_cpu_fallback.cpp:17.)
return torch._C._nn.upsample_nearest1d(input, output_size, scale_factors)
- Dominant language
- C++
- Stars
- 2.6k
- Forks
- 338
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/DirectML
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in microsoft/DirectML
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
autowarefoundation/autoware_universe#13413 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
automated-analysis bug memory-safety
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·