In D66278#1652021, @Jim wrote:

It can focus on whether the stack frame is created and not yet freed before the function call
for saving saved register or passing parameters or others.

In D66278#1646758, @lenary wrote:

Please may you explain a bit further why calls using varargs (when not passed by the stack) are allowed to be tail-call-optimised?

I feel the justification would be good documentation to go with the patch, and will help out me and other reviewers.

In D53291#1266158, @xudaliang.pku wrote:

But, I was not sure what rv32e and ilp32e really meaans. There is still something not clearly. Is the march rv32e only means that the regs only contains x0-x15 ? And the ABI ilp32e means Stack Alignment and calling convention, etc (see in https://github.com/riscv/riscv-elf-psabi-doc/blob/master/riscv-elf.md#rv32e-calling-convention )?

In D53291#1266082, @kito-cheng wrote:

rv32e arch and ilp32e ABI is decoupling is GCC, that's mean rv32i with ilp32e is possible, so I would suggest separate two thing.

Oh, and by the way, if the user really wants to use a load, they can easily force that by writing a global const (or single element initialized array to be really sure).

In D52962#1258544, @psnobl wrote:

Wouldn't it better to put more complicated constants (requiring 4 and more instructions to materialize) in constant pool and load them from there?

This pass already handles that indeed.

Can something similar to this be done where the user is a load or store?