make valgrind_toggle and valgrind_supported_platform private (pytorch…

…#46718)

make valgrind_toggle and valgrind_supported_platform private (pytorch…

…#46718)

gate load_library tests behind BUILD_TEST=1 (pytorch#46556)

ghstack-source-id: 9147465bd7eb251b1b65f3f7d08861e1cd560214
Pull Request resolved: pytorch#46550

[JIT] Improve class type annotation inference (pytorch#46422)

**Summary**
In `try_ann_to_type`, if an annotation has an attribute named
`__torch_script_class__`, it is assumed to be a TorchScript class that
has already been scripted. However, if it is a class that extends
another class, this code path causes a crash because it looks up the
JIT type for the class by name in the compilation unit. This JIT type
obviously cannot exist because inheritance is not supported.

This commit fixes this by looking up the qualified name of a class
in torch.jit._state._script_class in order to ascertain whether it has
already been scripted (instead of looking for a `__torch_script_class__`
attribute on the class object.

**Test Plan**
This commit adds a unit test consisting of the code sample from the
issue that reported this problem.

**Fixes**
This commit fixes pytorch#45860.

ghstack-source-id: 6fe19a45c694c1f9d7fb0e77bc72bd03ef2bf160
Pull Request resolved: pytorch#45940

[1.7] Remove torch.vmap (pytorch#45571)

torch.vmap is a prototype feature and should not be in the stable
binary. This PR:
- Removes the `torch.vmap` API
- Removes the documentation entry for `torch.vmap`
- Changes the vmap tests to use an internal API instead of `torch.vmap`.

Test Plan:
- Tested locally (test_torch, test_type_hints, test_vmap), but also wait
for CI.

Revert "[release/1.6] .circleci: Don't use SCCACHE for windows releas…

…e builds (pytorch#42024)"

This reverts commit 994b37b.

Revert "[release/1.6] .circleci: Don't use SCCACHE for windows releas…

…e builds (pytorch#42024)"

This reverts commit 994b37b.

[release/1.6] [JIT] Dont include view ops in autodiff graphs (pytorch…

…#42029)

* Dont include view ops in autodiff graphs

* skip view ops in autodiff testing

* two more tests

* appease calng format

* Pacify clang-format

Co-authored-by: eellison <[email protected]>
Co-authored-by: Nikita Shulga <[email protected]>

[jit] fix tuple alias analysis (pytorch#41992)

Previously when analyzing a TupleConstruct, we ignored the aliasing
information of the inputs and simply marked all elements of the returned
tuple as wildcards. But since we can fully reason about the contents of
a tuple statically, we should be able to assign them aliasing
information.

This analysis was not only incomplete but produced incorrect results,
since if `a` is not a wildcard, `a noalias wilcard`. So if we looked at
`tuple(a)` and reported the aliasing info as `tuple(wildcard)`, then
`tuple[0] noalias a`, which is...wrong.

scatter/gather - check that inputs are of the same dimensionality (py…

…torch#41890)

Co-authored-by: Nikita Vedeneev <[email protected]>