Update ReplaceAddMMWithLinearPass to use new pass interface

[DrJessop]

Summary: As titled, now correctly setting the modified bit.

Differential Revision: D86909981

[pytorch-bot[bot]]

:link: Helpful Links

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

• :page_facing_up: Preview Python docs built from this PR

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

:x: 1 Cancelled Job, 6 Unrelated Failures

As of commit b74340f70044f471d5bf06c4a4a599129709aed6 with merge base 6de1f4e1e28ced983d1ce1571f8ae0d443f73bfb ():

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

• periodic / gather-models (gh)

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

• pull / unittest / linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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

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

• pull / android / run-emulator (gh) (trunk failure) The process '/usr/bin/sh' failed with exit code 255
• pull / test-moshi-linux / linux-job (gh) (trunk failure) RuntimeError: Could not load libtorchcodec. Likely causes:
• pull / unittest / macos / macos-job (gh) (trunk failure) backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• pull / unittest-editable / linux / linux-job (gh) (trunk failure) backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• pull / unittest-editable / macos / macos-job (gh) (trunk failure) backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe

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

[meta-codesync[bot]]

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

[github-actions[bot]]

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.