Add MLX integer support for aten.bitwise_and

[yadferhad]

Summary

Fixes #18925

aten.bitwise_and currently goes through the bool-only LogicalAndNode path in the MLX delegate, which means integer tensors do not lower correctly. This switches aten.bitwise_and to a dedicated BitwiseAndNode while keeping aten.logical_and on the existing logical path.

This change:

• adds BitwiseAndNode to the MLX schema
• adds exec_bitwise_and() to the MLX interpreter runtime
• registers aten.bitwise_and.Tensor and aten.bitwise_and.Scalar as table-driven MLX binary ops
• keeps aten.logical_and on the existing bool-only logical path
• adds MLX op tests for bool, integer, and scalar bitwise_and

Test plan

• python3 -m py_compile backends/mlx/ops.py backends/mlx/test/test_ops.py
• python3 backends/mlx/serialization/generate.py
• PYTHONPATH=src python3 -m executorch.backends.mlx.test.run_all_tests --list | rg 'bitwise_and'
  • in a local dev env, this registers:
    • bitwise_and_bool
    • bitwise_and_int
    • bitwise_and_scalar

cc @metascroy

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

⚠️ 12 Awaiting Approval

As of commit 434fd1c with merge base 851cffb ():

AWAITING APPROVAL - The following workflows need approval before CI can run:

• Build documentation (gh)
• Build Presets (gh)
• Cadence Build & Test (gh)
• Lint (gh)
• MLX (gh)
• periodic (gh)
• pull (gh)
• Test ARM Backend (gh)
• Test CoreML Backend (gh)
• Test QNN Backend (gh)
• Test Vulkan Backend (gh)
• Test XNNPACK Backend (gh)

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

[meta-cla]

Hi @yadferhad!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[yadferhad]

@pytorchbot label "release notes: apple"

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[metascroy]

Hi @yadferhad! Thanks for the PR!

Overall it looks great, just two follow-up requests:

1. There are some merge conflicts. Can you resolve them?
2. Can you paste a screenshot of passing tests for bitwise_and in the PR summary?

Also note that we currently have a PR merge freeze until our CI is healthy again, but hopefully we can get this merged next week

[pytorch-bot]

The following ciflow label(s) have been added but CI has not been triggered yet because the workflows are awaiting approval:

• ciflow/mlx

Once a maintainer approves the workflows (scroll to the bottom of the PR page), the corresponding CI jobs will be triggered automatically. Please ping one of the reviewers if you do not have access to approve and run workflows.