add slice op in _is_share_obs_or_fq_op function to fix staticslice op in quantization

[barbecacov]

Summary

Caz xnnpack require the zero point of staticslice are same in inputs/outputs, so add slice op in _is_share_obs_or_fq_op to share quantization parameters

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 6 New Failures, 1 Cancelled Job

As of commit 47a8de6 with merge base c2d6f3d ():

NEW FAILURES - The following jobs have failed:

• Build Presets / linux (pybind, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11-aarch64) / build (gh)
  RuntimeError: Command docker exec -t 2f2a17369dac8dd68e929a4c0c406a0ec2d012717e240c32f93801a600051340 /exec failed with exit code 1
• Lint / lintrunner / linux-job (gh)
  >>> Lint for backends/xnnpack/quantizer/xnnpack_quantizer_utils.py:
• pull / test-eval_llama-mmlu-linux / linux-job (gh)
  RuntimeError: Command docker exec -t a677703abf3b6150b0e8efa3f817801323ee0b1dd3ad2c08d14decb6a5410a6b /exec failed with exit code 1
• pull / test-llama-runner-linux (fp32, xnnpack+custom+qe, linux.arm64.2xlarge, executorch-ubuntu-22.04-gc... / linux-job (gh)
  RuntimeError: Command docker exec -t 4e9bc6bcebb00ab3d597acf44f59ce1e535a36879b422e96c460aae69bc4acb2 /exec failed with exit code 1
• pull / test-phi-3-mini-runner-linux / linux-job (gh)
  AttributeError: 'StaticCacheConfig' object has no attribute 'get'
• pull / unittest / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

CANCELLED JOB - The following job was cancelled. Please retry:

• Build documentation / build (buck2) / Build doc (gh)
  ##[error]The operation was canceled.

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

[facebook-github-bot]

Hi @barbecacov!

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 [email protected]. Thanks!

[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.

[mcr229]

did you need all of these? I think slice.Tensor should be sufficient right?

[barbecacov]

Sorry, i am not sure. May just torch.ops.aten.slice.Tensor

[digantdesai]

@barbecacov I think you need to sign the CLA before we can merge this. Thanks for the fix BTW.

[barbecacov]

@digantdesai Thank you. I just signed.

[mcr229]

failures don't seem relevant. I'll stamp

[barbecacov]

@digantdesai Hello, is it ok to merge to master branch?

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.