Update Cortex-M backend status from proof of concept to beta#18690
Update Cortex-M backend status from proof of concept to beta#18690rascani wants to merge 2 commits intopytorch:mainfrom
Conversation
Co-authored-by: Claude <noreply@anthropic.com>
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/18690
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New Failure, 2 Unrelated FailuresAs of commit 6ffc8c6 with merge base 6823b33 ( NEW FAILURE - The following job has failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
BROKEN TRUNK - The following job failed but was present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
backends/cortex_m/README.md
Outdated
|
|
||
| > [!NOTE] | ||
| > WIP. This is a temporary/placeholder backend for Cortex-M CPUs. It is not intended to be used in production, but rather as a proof of concept. Things will change without notice. | ||
| > Beta. This backend is functional and tested but APIs may change between releases. |
There was a problem hiding this comment.
For Beta, we start adhering to public API deprecation and lifecycle policy
https://docs.pytorch.org/executorch/main/api-life-cycle.html
There was a problem hiding this comment.
Updated to remove the comment about APIs changing, and added some details about how it has been tested so far.
@AdrianLundell - let me know if you're okay with this. I'll wait on merging until you're on board.
Co-authored-by: Claude <noreply@anthropic.com>
As discussed in 4/1/26 partner sync.