Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dynamo][cpp-guards] Improve recompilation reason logic for NO_TENSOR_ALIASING guard #125439

Closed
wants to merge 4 commits into from

Conversation

Copy link

pytorch-bot bot commented May 2, 2024

🔗 Helpful Links

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

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

✅ No Failures

As of commit be8b9bd with merge base 3b5f6b1 (image):
💚 Looks good so far! There are no failures yet. 💚

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

…r NO_TENSOR_ALIASING guard"

cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx chenyang78 kadeng chauhang

[ghstack-poisoned]
anijain2305 added a commit that referenced this pull request May 2, 2024
…_ALIASING guard

ghstack-source-id: 63b5c844aa7529fd7fec0592b87c51c6ab0fdfa6
Pull Request resolved: #125439
@@ -1305,9 +1301,6 @@ class NO_TENSOR_ALIASING : public RelationalGuard {
if (!result) {
std::stringstream fail_reason;
Copy link
Member

Choose a reason for hiding this comment

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

Could just use a regular std::string here?

@@ -2419,7 +2440,16 @@ def get_guard_fail_reason(
# walk through this list and find the guard that failed. This is
# very important for symbolic shape guards which are currently
# installed as a lambda guard and can encompass a long list of code_parts.
if len(verbose_code_parts) == 1:

if (
Copy link
Member

Choose a reason for hiding this comment

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

Refactor this conditional?

…r NO_TENSOR_ALIASING guard"

cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx chenyang78 kadeng chauhang

[ghstack-poisoned]
anijain2305 added a commit that referenced this pull request May 2, 2024
…_ALIASING guard

ghstack-source-id: 0b135e6530e40c316777bb502ba0d835b7cbaa34
Pull Request resolved: #125439
…r NO_TENSOR_ALIASING guard"

cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx chenyang78 kadeng chauhang

[ghstack-poisoned]
@anijain2305 anijain2305 added the topic: not user facing topic category label May 2, 2024
@anijain2305
Copy link
Contributor Author

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label May 2, 2024
@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

pytorchmergebot pushed a commit that referenced this pull request May 3, 2024
pytorchmergebot pushed a commit that referenced this pull request May 4, 2024
Improves the guard overhead of MobileBert model with nn module guards from 92000 units to 20000 units.

Pull Request resolved: #124522
Approved by: https://github.com/jansel
ghstack dependencies: #125439, #125421
pytorchmergebot pushed a commit that referenced this pull request May 4, 2024
@github-actions github-actions bot deleted the gh/anijain2305/312/head branch June 5, 2024 01:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants