Skip to content

Treat a missing rounding mode in div_out_mode as true division - #24178

Open
aliafzal wants to merge 3 commits into
pytorch:mainfrom
aliafzal:export-D127746755
Open

aliafzal wants to merge 3 commits into
pytorch:mainfrom
aliafzal:export-D127746755

Conversation

@aliafzal

Copy link
Copy Markdown
Contributor

Summary:
div.Tensor_mode(a, b, rounding_mode=None) is true division. The HiFi div_out_mode sent None to the non-optimized path, where mode_is_trunc was false and the code fell through to floor_divide (its comment assumed the mode "must be floor"). So 7 / 2 returned 3 and -7 / 2 returned -4. The kernel now delegates to div_out when mode has no value, which is what the portable and Fusion G3 div_out_mode already do.

Found by the Jarvis nightly operator tests: on nxp_rt600 (HiFi4), test_aten_div_out_mode fails every case where FACTO picks rounding_mode=None (25 of 50, all with max_abs_diff ≈ 0.99). DLA, which uses a different kernel, passes all 50.

Differential Revision: D127746755

…torch#24176)

Summary:

`add.Scalar(Tensor self, Scalar other, Scalar alpha=1)` takes `alpha` positionally, but `add.Tensor(Tensor self, Tensor other, *, Scalar alpha=1)` takes it as keyword-only, and the same holds for `sub`. When `alpha` was the third positional argument, `get_replacement` passed it through `*args[2:]`, and building the `.Tensor` node raised `RuntimeError: aten::add() takes 2 positional argument(s) but 3 was/were given`. The 3-argument path now passes `args[:2]` and moves `alpha` into `kwargs`, so `get_replacement` always gets 2 args and no longer forwards extra ones. The Arm `ReplaceScalarWithTensorByProfilePass` subclass routes through the same base `call_operator`, so it gets the fix too for edge `add/sub.Scalar`. `torch.ops.aten.add/sub.Scalar` with a positional `alpha` still pass through unreplaced, as before. The changed path previously always raised, so no graph that worked before is affected.

Found by the Jarvis nightly operator tests: `test_aten_add_scalar_out` fails 13 of 24 FACTO cases (every case with an explicit `alpha`) on nxp, DLA and Artemis v3/v4.

]

Differential Revision: D127746753
Summary:
`pow.Tensor_Scalar(int32, 2.0)` returns float32, but the `mul.Tensor(x, x)` chain that `ReplacePowWithMulPass` emits stays int32. The pass copied the float32 `meta` onto the int32 `mul` nodes, so the lowered program's output dtype no longer matched the eager reference. The pass now gives up when the input dtype differs from the `pow` output dtype.

Found by the Jarvis nightly operator tests: `test_pow_Tensor_Scalar_out` cases 14 and 23 (int32 input, exponent 2.0) fail on nxp, DLA, Artemis v3/v4 and CPU with `The label tensor ... dtype shall be torch.int32, but now is torch.float32`.

Differential Revision: D127746754
Summary:
`div.Tensor_mode(a, b, rounding_mode=None)` is true division. The HiFi `div_out_mode` sent `None` to the non-optimized path, where `mode_is_trunc` was false and the code fell through to `floor_divide` (its comment assumed the mode "must be floor"). So `7 / 2` returned 3 and `-7 / 2` returned -4. The kernel now delegates to `div_out` when `mode` has no value, which is what the portable and Fusion G3 `div_out_mode` already do.

Found by the Jarvis nightly operator tests: on nxp_rt600 (HiFi4), `test_aten_div_out_mode` fails every case where FACTO picks `rounding_mode=None` (25 of 50, all with `max_abs_diff ≈ 0.99`). DLA, which uses a different kernel, passes all 50.

Differential Revision: D127746755
@pytorch-bot

pytorch-bot Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

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

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

✅ No Failures

As of commit 817eeeb with merge base a90db24 (image):
💚 Looks good so far! There are no failures yet. 💚

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

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 27, 2026
@meta-codesync

meta-codesync Bot commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

@aliafzal has exported this pull request. If you are a Meta employee, you can view the originating Diff in D127746755.

@github-actions

Copy link
Copy Markdown

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.

This branch was successfully deployed

1 active deployment
cadence — 817eeeb9 Deployed Oct 27, 2026 by aliafzal via hifi-op-test / hifi4 #34788
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants