In D135579#4417921, @foad wrote:

This broke regenerating checks for tests like test/CodeGen/AMDGPU/GlobalISel/regbankselect-amdgcn.s.buffer.load.ll which use -simplify-mir and do not print the fixedStack info. Can you fix update_mir_test_checks to cope, or should we remove -simplify-mir from files with generated checks?

Re-process MachineOperands when kill/dead flags are added. Adding those on implicit operands might re-arrange the whole list of MOs in a MachineInstr.

Any additional feedback?

@nhaehnle @arsenm Thank you for having a look at this patch. I unfortunately don't have commit "powers", would it be possible for one of you to commit on my behalf?
Here is the commit header I usually have: Gaëtan Bossu <gaetan.bossu@amd.com>, if you need it. Thank you in advance :)

In D135580#3961470, @arichardson wrote:

In D135580#3960700, @gbossu wrote:

Rebase on latest main, otherwise tests seem to timeout.

You can ignore the libfuzzer test failure - it's unrelated. I filed https://github.com/llvm/llvm-project/issues/59197 a few days ago since I noticed it failing on almost all reviews.

Rebase on latest main, otherwise tests seem to timeout.

Rebase on latest main, otherwise tests seem to timeout.

Remove print-stack-update.mir test input file and just re-run update_mir_test_checks on the existing file instead.

Thank you! Could someone commit the change on my behalf? I do not think I have write access, since it's my first patch here.

Fix coding style & useless assignment

Update email address in commit...