Skip to content

Conversation

@bwasti
Copy link
Contributor

@bwasti bwasti commented Nov 6, 2019

Summary: ..

Test Plan: ..

Reviewed By: ZolotukhinM

Differential Revision: D18340212

Summary: ..

Test Plan: ..

Reviewed By: ZolotukhinM

Differential Revision: D18340212

fbshipit-source-id: 39c8e84901452fc71efde7f870ea1f5c3e933eaf
@bwasti bwasti requested a review from apaszke as a code owner November 6, 2019 00:46
@facebook-github-bot facebook-github-bot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Nov 6, 2019
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D18340212

@facebook-github-bot
Copy link
Contributor

This pull request has been merged in ee21142.

@eellison
Copy link
Contributor

eellison commented Nov 6, 2019

Doesn't this break any custom pass any external user will have ? (e.g. torch_tvm). I don't know how public we consider the api to be. What exactly was the motivation for this change ?

cc @zdevito @ZolotukhinM

@ilia-cher
Copy link
Contributor

why did we do this and what is the impact on TVM pass?

@ZolotukhinM
Copy link

I think the only external user so far is torch_tvm which @bwasti wrote. The motivation to do this was to be able to fix-up things after optimizations (e.g. after fusion). Ideally, I think we should have a mechanism to register passes before and after the standard pipeline. So far my understanding was that it's not widely used so we can change it freely if the other option is more convenient.

@eellison
Copy link
Contributor

eellison commented Nov 8, 2019

I agree we should have a mechanism to run before and after the pipeline. Still, i wouldn't be surprised if there are some users of the api somewhere and it would be preferable if this was done in OSS and not phabricator.

At any rate, this comment should be updated:
https://github.com/pytorch/pytorch/blob/master/torch/csrc/jit/pass_manager.h#L6

@bwasti
Copy link
Contributor Author

bwasti commented Nov 8, 2019

OSS == Phabricator because of export, no? There are effectively no passes in JIT today, so I don't think it's much of an issue. If folks are using this mechanism and they find this breaks their stuff, they'll file an issue and we can go from there

Agreed on updating the comment

@eellison
Copy link
Contributor

eellison commented Nov 8, 2019

It's only partially OSS; you can't see how the PR was reviewed if you're external.

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

Labels

Merged oncall: jit Add this issue/PR to JIT oncall triage queue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants