Import MKL via //third-party/mkl targets

[MatzeB]

Summary:
This is a step towards upgrading the MKL library and using a buckified targets rather than importing from TP2.

• Add new //third-party/mkl:mkl_xxx targets that are currently aliases to third-party//IntelComposerXE:mkl_xxx.
• Switch usage of external_deps = [("IntelComposerXE", None, "mkl_xxx")] to deps = ["fbsource//third-party/mkl:mkl_xxx"]

Note that this only changes references to mkl_xxx references in IntelComposerXE but not references to "svml" or "ipp*".

Test Plan: sandcastle

Differential Revision: D57360438

[pytorch-bot]

This appears to be a diff that was exported from phabricator, but the PR author does not have sufficient permissions to run CI. @MatzeB, please do step 2 of internal wiki to get write access so you do not need to get CI approvals in the future. If you think this is a mistake, please contact the Pytorch Dev Infra team.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/126371

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (4 Unrelated Failures)

As of commit 2d2bf82 with merge base c860df5 ():

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / linux-focal-cuda11.8-py3.10-gcc9 / test (distributed, 1, 3, linux.8xlarge.nvidia.gpu) (gh) (similar failure)
  distributed/_composable/fsdp/test_fully_shard_training.py::TestFullyShardCustomForwardMethod::test_register_fsdp_forward_method
• pull / linux-focal-cuda12.1-py3.10-gcc9-sm86 / test (default, 2, 5, linux.g5.4xlarge.nvidia.gpu) (gh) (similar failure)
  test_foreach.py::TestForeachCUDA::test_binary_op_list_error_cases__foreach_add_cuda_bfloat16

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• Lint / lintrunner-noclang / linux-job (gh) (trunk failure)
  >>> Lint for torch/onnx/_internal/onnx_proto_utils.py:
• pull / linux-focal-cuda12.1-py3.10-gcc9-sm86 / test (default, 5, 5, linux.g5.4xlarge.nvidia.gpu) (gh) (trunk failure)
  inductor/test_flex_attention.py::TestTemplatedSDPA::test_builtin_score_mods_bfloat16_score_mod1

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

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

[facebook-github-bot]

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

[pytorch-bot]

This appears to be a diff that was exported from phabricator, but the PR author does not have sufficient permissions to run CI. @MatzeB, please do step 2 of internal wiki to get write access so you do not need to get CI approvals in the future. If you think this is a mistake, please contact the Pytorch Dev Infra team.

[facebook-github-bot]

@pytorchbot merge -f 'Landed internally'

(Initiating merge automatically since Phabricator Diff has merged, using force because this PR might not pass merge_rules.json but landed internally)

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here