[Inductor][CPP] Add Min/Max with VecMask

[leslie-fang-intel]

Stack from ghstack (oldest at bottom):

• -> #126841

Summary Fix issue: https://github.com/pytorch/pytorch/issues/126824 which is missing the support of min/max with VecMask.

TestPlan

python test/inductor/test_torchinductor_opinfo.py -k test_comprehensive_clamp_max_cpu_bool
python test/inductor/test_torchinductor_opinfo.py -k test_comprehensive_clamp_min_cpu_bool

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @voznesenskym @penguinwu @EikanWang @Guobing-Chen @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang

[pytorch-bot[bot]]

:link: Helpful Links

:test_tube: See artifacts and rendered test results at hud.pytorch.org/pr/126841

• :page_facing_up: Preview Python docs built from this PR
• :page_facing_up: Preview C++ docs built from this PR
• :question: 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.

:white_check_mark: You can merge normally! (1 Unrelated Failure)

As of commit de9c5b9603d48ba5d6126f6ae8252475fd700671 with merge base 6079c5091091d872b8dafbaa4e31a5b6194647ad ():

UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:

• inductor / rocm6.1-py3.8-inductor / test (inductor, 1, 1, linux.rocm.gpu.2) (gh) (#128871) 'Test'

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

[leslie-fang-intel]

Hi @isuruf, these 2 PRs in the ghstack may have conflict with https://github.com/pytorch/pytorch/pull/124021. We prefer to land 124021 at first. Then I will rebase to land the PRs here. Does it sound good to you?

[isuruf]

Sounds good to me.

[leslie-fang-intel]

@pytorchbot merge

[pytorchmergebot]

Merge failed

Reason: This PR needs a release notes: label If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example @pytorchbot label "topic: not user facing"

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

Details for Dev Infra team

Raised by workflow job

[leslie-fang-intel]

@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

[DanilBaibak]

@pytorchbot revert -m "Blocks reverting of the broken PR" -c ghfirst

[pytorchmergebot]

@pytorchbot successfully started a revert job. Check the current status here. Questions? Feedback? Please reach out to the PyTorch DevX Team

[pytorchmergebot]

@leslie-fang-intel your PR has been successfully reverted.

[DanilBaibak]

Hi @leslie-fang-intel! Sorry, I need to revert your PRs because they block reverting of broken PR. Please rebase your PRs and merge them as soon as CI is green.

[isuruf]

@pytorchbot rebase

[pytorchmergebot]

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

[pytorchmergebot]

Rebase failed due to

Aborting rebase because rebasing the branch resulted in the same sha as the target branch.
This usually happens because the PR has already been merged.  Please rebase locally and push.

Raised by https://github.com/pytorch/pytorch/actions/runs/9459495597

[leslie-fang-intel]

@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