…g torch.compile infrastructure

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]

…t overriding torch.compile infrastructure"

After discussing offline with bdhirsh, we reached the conclusion that while tracing torch function modes it does not make sense to respect user overrides on functions we are running (ie the torch profiler for example) during the execution of torch.compile code, since we are symbolically respecting those modes during tracing. So, we pop all modes before tracing begins and restore them after tracing ends. Note the symbolic torch function mode stack contains all of the modes before they are popped. 




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

[ghstack-poisoned]