Add Half support for cummax, cummin, cumprod, logcumsumexp, and prod on CPU

[CaoE]

Add Half support for cummax, cummin, cumprod, logcumsumexp, and prod on CPU.

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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! (2 Unrelated Failures)

As of commit bccbab0 with merge base 64f3260 ():

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• periodic / macos-12-py3-x86-64 / build (gh)

BROKEN TRUNK - The following job failed but was present on the merge base:

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

• periodic / linux-focal-cuda11.8-py3.9-gcc9 / test (multigpu, 1, 1, linux.g5.12xlarge.nvidia.gpu) (gh)

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

[CaoE]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

[pytorchmergebot]

Merge failed

Reason: Command git -C /home/runner/work/pytorch/pytorch rebase origin/main returned non-zero exit code 1

Rebasing (1/1)
Auto-merging test/test_mps.py
CONFLICT (content): Merge conflict in test/test_mps.py
Auto-merging test/test_reductions.py
Auto-merging torch/testing/_internal/common_methods_invocations.py
Auto-merging torch/testing/_internal/opinfo/definitions/_masked.py
error: could not apply 1a5df2a9f8b... Add Half support for cummax, cummin, cumprod, logcumsumexp, and prod on CPU (#112132)
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 1a5df2a9f8b... Add Half support for cummax, cummin, cumprod, logcumsumexp, and prod on CPU (#112132)

Details for Dev Infra team

Raised by workflow job

[cpuhrsch]

@CaoE - The topic for these changes should be "improvements". They every much are user facing since they extend operator coverage to a new dtype on a device. Please update the other PRs as well.

[CaoE]

@cpuhrsch Do other PRs also require release note: nn ?

[cpuhrsch]

@CaoE - I'm not sure. We could also use "release notes: intel". Seems appropriate?

[CaoE]

@cpuhrsch I added a new label "release notes: half" for half support.

[cpuhrsch]

@CaoE - Please use an existing label and delete the one you created. It won't work with our release notes setup. I think release notes: intel is appropriate.

[CaoE]

@cpuhrsch Removed & deleted release notes: half and use release notes: intel instead.d

[cpuhrsch]

@pytorchbot rebase

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

Successfully rebased fp16_ops3 onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout fp16_ops3 && git pull --rebase)

[cpuhrsch]

@pytrchbot merge

[cpuhrsch]

@pytorchbot rebase

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

Successfully rebased fp16_ops3 onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout fp16_ops3 && git pull --rebase)

[CaoE]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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