Skip to content

Conversation

@zdevito
Copy link
Contributor

@zdevito zdevito commented May 29, 2019

Stack from ghstack:

Summary: Uses the analyzeCustomOp rule (renamed analyzeConservative)
to support CallFunction, assuming we do not know the function implementation.
When we have a know function target, and a way to summarize alias info
we can make the analysis more accurate.

Cleans up seemingly dead code in alias analysis and fixes a bug in
analyzeCustomOp where inputs are not marked as potentially aliasing the
wildcard set.

Test Plan: test_jit.py

Differential Revision: D15542512

Summary: Uses the analyzeCustomOp rule (renamed analyzeConservative)
to support CallFunction, assuming we do not know the function implementation.
When we have a know function target, and a way to summarize alias info
we can make the analysis more accurate.

Cleans up seemingly dead code in alias analysis and fixes a bug in
analyzeCustomOp where inputs are not marked as potentially aliasing the
wildcard set.

Test Plan: test_jit.py
@pytorchbot pytorchbot added oncall: jit Add this issue/PR to JIT oncall triage queue module: internals Related to internal abstractions in c10 and ATen labels May 29, 2019
@zdevito zdevito requested a review from suo May 29, 2019 20:14
zdevito added 3 commits May 29, 2019 15:42
…hod"

Conservative alias analysis rules for CallFunction/CallMethod

Summary: Uses the analyzeCustomOp rule (renamed analyzeConservative)
to support CallFunction, assuming we do not know the function implementation.
When we have a know function target, and a way to summarize alias info
we can make the analysis more accurate.

Cleans up seemingly dead code in alias analysis and fixes a bug in
analyzeCustomOp where inputs are not marked as potentially aliasing the
wildcard set.

Test Plan: test_jit.py

gh-metadata: pytorch pytorch 21087 gh/zdevito/41/head
…hod"

Conservative alias analysis rules for CallFunction/CallMethod

Summary: Uses the analyzeCustomOp rule (renamed analyzeConservative)
to support CallFunction, assuming we do not know the function implementation.
When we have a know function target, and a way to summarize alias info
we can make the analysis more accurate.

Cleans up seemingly dead code in alias analysis and fixes a bug in
analyzeCustomOp where inputs are not marked as potentially aliasing the
wildcard set.

Test Plan: test_jit.py

gh-metadata: pytorch pytorch 21087 gh/zdevito/41/head
…hod"

Conservative alias analysis rules for CallFunction/CallMethod

Summary: Uses the analyzeCustomOp rule (renamed analyzeConservative)
to support CallFunction, assuming we do not know the function implementation.
When we have a know function target, and a way to summarize alias info
we can make the analysis more accurate.

Cleans up seemingly dead code in alias analysis and fixes a bug in
analyzeCustomOp where inputs are not marked as potentially aliasing the
wildcard set.

Test Plan: test_jit.py

gh-metadata: pytorch pytorch 21087 gh/zdevito/41/head
@zou3519 zou3519 deleted the gh/zdevito/41/head branch May 30, 2019 18:04
zdevito added a commit to zdevito/ATen that referenced this pull request May 30, 2019
Summary:
Pull Request resolved: pytorch/pytorch#21087
ghimport-source-id: 4fa6763ffecc7d2974b902dd9bd2bd9ac467bab7

Differential Revision: D15542512

Pulled By: zdevito

fbshipit-source-id: 2dcd673cd4c200d7a854347429d4f33a11793cbc
@facebook-github-bot
Copy link
Contributor

@zdevito merged this pull request in 6dc445e.

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

Labels

Merged module: internals Related to internal abstractions in c10 and ATen 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