pytorch / pytorch/executorch

[CMake] Decouple prim_ops from executorch

Open
#10,704 1 comment 0 reactions 3 assignees View on GitHub

@kirklandsign is already working on this.

Since May 6, 2025.

module: build/install triaged
Dominant language
Python
Stars
5k
Forks
1.2k
Avg merge
2d 10h
Merged PRs (30d)
581

Description

🚀 The feature, motivation and pitch

Right now we have executorch_core, and executorch(= executorch_core + prim_ops).

This is confusing, when people depend on executorch. Make prim_ops a separate library instead.

Similarly, we might need to revisit BUCK runtime/executor:program vs runtime/executor:program_no_prim_ops

Alternatives

No response

Additional context

No response

RFC (Optional)

No response

cc @larryliu0820 @jathu

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.