summaryrefslogtreecommitdiff
path: root/test/stacky.wasm.fromBinary
diff options
context:
space:
mode:
authorAshley Nelson <nashley@google.com>2024-12-19 14:49:16 -0800
committerGitHub <noreply@github.com>2024-12-19 14:49:16 -0800
commit4e1ae4aa5815fb474c829d15d7c93abee0ce14e3 (patch)
tree76920c4663773646fa1c56e0928f5776a5d4259e /test/stacky.wasm.fromBinary
parentdcec348ded6d7ab7bf4b758bdb92107e4262dbf4 (diff)
downloadbinaryen-4e1ae4aa5815fb474c829d15d7c93abee0ce14e3.tar.gz
binaryen-4e1ae4aa5815fb474c829d15d7c93abee0ce14e3.tar.bz2
binaryen-4e1ae4aa5815fb474c829d15d7c93abee0ce14e3.zip
[Outlining] Sort sequences by order appeared in function (#7164)
During function reconstruction, a walker iterates thru each instruction of a function, incrementing a counter to find matching sequences. As a result, the sequences of a function must be sorted by smallest start index, otherwise reconstruction will miss outlining a repeat sequence. I considered making a test for this commit, but the sort wasn't needed until the tests started running on GitHub infra. I'm not sure what specific architecture is causing the discrepancy in vector ordering, but let's introduce the sort to be safe.
Diffstat (limited to 'test/stacky.wasm.fromBinary')
0 files changed, 0 insertions, 0 deletions