ns for fx: move node I/O dtype mapping to be local instead of global

[vkuzo]

Stack from ghstack:

• ns for fx: additional bugfix for user defined functions #57028 ns for fx: additional bugfix for user defined functions
• ns for fx: allow comparing int8 to int8 for functionals #57027 ns for fx: allow comparing int8 to int8 for functionals
• ns for fx: add option to skip matching classes and functions #57026 ns for fx: add option to skip matching classes and functions
• ns for fx: support binary ops when adding unshadowed loggers for inputs #57025 ns for fx: support binary ops when adding unshadowed loggers for inputs
• ns for fx: bug fix for shadowing fp16 emulation patterns #57024 ns for fx: bug fix for shadowing fp16 emulation patterns
• ns for fx: add fp16 function shadowing #57023 ns for fx: add fp16 function shadowing
• ns for fx: allow user functions in shadowing #57022 ns for fx: allow user functions in shadowing
• ns for fx: move node I/O dtype mapping to be local instead of global #57021 ns for fx: move node I/O dtype mapping to be local instead of global

Summary:

To support shadows of custom functions, we need to allow user to
specify I/O type of the custom functions.

This PR is a cleanup in preparation for making the above happen.
We make the I/O dtype mappings be generated by a function instead
of a global variable. In the next PR, we will add a hook so user
can modify these mappings.

Test Plan:

python test/test_quantization.py TestFXNumericSuiteCoreAPIs

Differential Revision: D28030094

[facebook-github-bot]

💊 CI failures summary and remediations

As of commit 2f06fb4 (more details on the Dr. CI page):

---

• 1/2 failures possibly* introduced in this PR
  • 1/1 non-scanned failure(s)
• 1/2 tentatively recognized as flaky ❄️
  • Click here to rerun these jobs

---

❄️ 1 failure tentatively classified as flaky

but reruns have not yet been triggered to confirm:

pytorch_linux_xenial_cuda10_2_cudnn7_py3_gcc7_test2 (1/1)

Step: "Run tests" (full log | diagnosis details | 🔁 rerun) ❄️

Apr 27 17:01:21 RuntimeError: Process 0 terminated or timed out after 110.049307346344 seconds

Apr 27 17:01:21 ======================================================================
Apr 27 17:01:21 ERROR [110.073s]: test_nccl_high_priority_stream (__main__.TestDistBackendWithSpawn)
Apr 27 17:01:21 ----------------------------------------------------------------------
Apr 27 17:01:21 Traceback (most recent call last):
Apr 27 17:01:21   File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 374, in wrapper
Apr 27 17:01:21     self._join_processes(fn)
Apr 27 17:01:21   File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 566, in _join_processes
Apr 27 17:01:21     self._check_return_codes(elapsed_time)
Apr 27 17:01:21   File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 614, in _check_return_codes
Apr 27 17:01:21     raise RuntimeError('Process {} terminated or timed out after {} seconds'.format(i, elapsed_time))
Apr 27 17:01:21 RuntimeError: Process 0 terminated or timed out after 110.049307346344 seconds
Apr 27 17:01:21 
Apr 27 17:01:21 ----------------------------------------------------------------------
Apr 27 17:01:21 Ran 196 tests in 715.617s
Apr 27 17:01:21 
Apr 27 17:01:21 FAILED (errors=4, skipped=117)
Apr 27 17:01:21 
Apr 27 17:01:21 Generating XML reports...
Apr 27 17:01:21 Generated XML report: test-reports/dist-nccl/distributed.test_distributed_spawn/TEST-TestDistBackendWithSpawn-20210427164925.xml
Apr 27 17:01:21 Traceback (most recent call last):
Apr 27 17:01:21   File "test/run_test.py", line 1156, in <module>

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[facebook-github-bot]

@vkuzo merged this pull request in c4bec76.