Skip to content

Conversation

@Skylion007
Copy link
Collaborator

@Skylion007 Skylion007 commented Dec 10, 2022

Applies various automated fixes that reduces the number of spurious copies in torch, aten, and c10. I also inlined any default dtors that would have made the type trivially destructible.

Follow up to #89000

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @EikanWang

@pytorch-bot
Copy link

pytorch-bot bot commented Dec 10, 2022

🔗 Helpful Links

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

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

✅ No Failures

As of commit 9ef6c42:
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added the release notes: jit release notes category label Dec 10, 2022
@github-actions github-actions bot added module: cpu CPU specific problem (e.g., perf, algorithm) NNC labels Dec 10, 2022
@Skylion007 Skylion007 marked this pull request as ready for review December 11, 2022 16:47
@Skylion007
Copy link
Collaborator Author

Also ccing @ezyang since a lot of these accidental copies are of SymInts / SymFloats.

Copy link
Contributor

@ezyang ezyang left a comment

Choose a reason for hiding this comment

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

Would you consider helping us setup a lint for this? Only way to keep it fixed.

@ezyang
Copy link
Contributor

ezyang commented Dec 12, 2022

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Dec 12, 2022
@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@Skylion007
Copy link
Collaborator Author

Would you consider helping us setup a lint for this? Only way to keep it fixed.

I would love to but that would require closing #62011. These checks are already linted under places where lintrunner's clang-tidy is currently run, but that's a small fraction of the code base.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request Merged module: cpu CPU specific problem (e.g., perf, algorithm) NNC open source release notes: jit release notes category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants