Skip to content

Conversation

@JacobSzwejbka
Copy link
Contributor

@JacobSzwejbka JacobSzwejbka commented Nov 10, 2025

the .lib file comes from compiling aoti_cuda_shims on windows. Ideally we will not check this in but rather cross compile it on the fly from linux. Thats coming soonish.

We need the .lib file in order to lower for cuda windows backend. Cuda windows uses AOTI as the acceleration lib, AOTI generates executable code that calls into the shim. On windows you must provide a reference to all symbols you will link against (unlike linux) so we need the .lib artifact.

@pytorch-bot
Copy link

pytorch-bot bot commented Nov 10, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15713

Note: Links to docs will display an error until the docs builds have been completed.

⏳ 16 Pending, 2 Unrelated Failures

As of commit 0294060 with merge base 234c288 (image):

BROKEN TRUNK - The following jobs failed but were 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.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Nov 10, 2025
@github-actions
Copy link

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

src_dir="backends/cuda/runtime/",
src_name="aoti_cuda_shims.lib",
dst="executorch/data/bin/",
dependent_cmake_flags=[],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you need to dependent on EXECUTORCH_BUILD_CUDA

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont want to be dependent on that build flag. I want to always put it in the pip package because this is for the AoT flow which is no longer gated by the cmake flag

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could technically try to gate this behind if we are building cuda, but its just a temporary hack anyway till we have cross compiling so I think its fine to just land.

@JacobSzwejbka JacobSzwejbka merged commit 054b15d into main Nov 10, 2025
159 of 171 checks passed
@JacobSzwejbka JacobSzwejbka deleted the check-in-lib branch November 10, 2025 21:58
JacobSzwejbka added a commit that referenced this pull request Nov 10, 2025
the .lib file comes from compiling aoti_cuda_shims on windows. Ideally
we will not check this in but rather cross compile it on the fly from
linux. Thats coming soonish.

We need the .lib file in order to lower for cuda windows backend. Cuda
windows uses AOTI as the acceleration lib, AOTI generates executable
code that calls into the shim. On windows you must provide a reference
to all symbols you will link against (unlike linux) so we need the .lib
artifact.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants