[PATCH] D123935: llvm-reduce: Preserve frame index values when cloning function

Matt Arsenault via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Mon Apr 18 07:10:20 PDT 2022


arsenm created this revision.
arsenm added reviewers: markus, qcolombet, aeubanks, MatzeB, reames.
Herald added a subscriber: arphaman.
Herald added a project: All.
arsenm requested review of this revision.
Herald added a subscriber: wdng.
Herald added a project: LLVM.

Previously the specific values used for fixed frame indexes was in
reverse order in the cloned function from the original, and a map was
used to adjust all frame indexes to the potentially new values. Insert
the fixed objects in reverse to avoid this. This simplifies other
code, since now we don't need to track down all frame indexes. This
will allow targets that store frame indexes in MachineFunctionInfo to
simply copy the values.

      

Note this isn't directly observable in the test since the resulting
MIR print/parse can shuffle the IDs around (in particular the final
serialization implicitly strips out dead objects).


https://reviews.llvm.org/D123935

Files:
  llvm/tools/llvm-reduce/ReducerWorkItem.cpp

-------------- next part --------------
A non-text attachment was scrubbed...
Name: D123935.423382.patch
Type: text/x-patch
Size: 5791 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20220418/15074fc2/attachment.bin>


More information about the llvm-commits mailing list