[ET-VK] Support different input layouts in q8ta_binary operator

[SS-JIA]

Stack from ghstack (oldest at bottom):

• [ET-VK][ez][qconv] Add auto-selection to prefer im2col for q8ta_conv2d #17568
• [ET-VK][q8ta] Fix addmm arg indexing in QuantizedLinearMatch #17567
• [ET-VK][q8ta] Add q8ta_linear_gemv op for batch-1 int8 linear #17566
• [ET-VK][q8ta] Add q8ta_linear operator for int8 quantized linear #17565
• [ET-VK][export] Update tensor representation sync logic to allow for flexibility in memory layouts #17564
• -> [ET-VK] Support different input layouts in q8ta_binary operator #17563
• [ET-VK][ez] Always partition batch norm as it will be fused #17508
• [ET-VK] Add fused q8ta_relu unary operator for int8x4 tensors #17507
• [ET-VK][qconv] Add apply_relu support to q8ta conv operators #17506
• [ET-VK][qconv] Pad weight_sums buffer to multiple-of-4 alignment #17505
• [ET-VK][qconv] Fix depthwise weight_sums sum dimension #17504

Previously, the q8ta_binary operator required both inputs to use the same memory layout. This was enforced by using a single in_layout specialization constant for both input buffers. However, some models may have inputs with different layouts (e.g., 4W4C and 4C1W) that share the same packed dimension and block size, which should be compatible for binary operations. This change introduces a separate other_layout specialization constant for the second input, allowing the shader to correctly load from input_b using its actual layout while input_a continues to use in_layout. The C++ side now passes both layout hashes as separate specialization constants to the shader.

Differential Revision: D93768638

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 3 New Failures

As of commit 04e6b54 with merge base 7b843e4 ():

NEW FAILURES - The following jobs have failed:

• pull / test-openvino-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 0d2a86dd667b2ed637d7da258b9e03f90038771f81b03a574f1e6ed356da1265 /exec failed with exit code 1
• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t 7d65fe1df9d77dd7a916755cbf2ba7336c7d5cddbecbf1cf723db9882db968a6 /exec failed with exit code 1
• Test CUDA Builds / export-model-cuda-artifact (openai, whisper-small, non-quantized) / linux-job (gh)
  RuntimeError: Command docker exec -t 6e8adb847c97b7b7ff7e7e5d358ba18417ffb54a471fed34a2be7f2ed667be81 /exec failed with exit code 1

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

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.