[starwarfan]

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

• N
• Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

• Affects user behaviors
• Contains CI/CD configuration changes
• Contains documentation changes
• Contains experimental features
• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• N
• Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• Unit test
• Integration test
• Benchmark (add benchmark stats below)
• Manual test (add detailed scripts or steps below)
• Other

6. Release note

None

[zoowii]

Since many other opcodes also manipulate the stack, will other instructions need to be modified?

It would be good to document a proposed solution first.

[zoowii]

Evaluate the proposal document. If it has a significant impact on performance and a large impact on the code base, can we statically analyze during compilation to detect situations where the stack depth of instructions cannot be determined, and then degrade to the interpreter?

[starwarfan]

I'll write a document first. If the backend can handle the mem2reg optimization well, I think most store and load instructions from same location would be eliminated in final output.