User Details
- User Since
- Jul 14 2020, 5:33 AM (39 w, 5 h)
Sun, Apr 11
Thu, Apr 8
Fix error.
Wed, Apr 7
Sun, Mar 21
Ping.
Fri, Mar 19
Thu, Mar 18
Hi @rogfer01 ! It is reasonable to me. But I think the instruction of BuildMI(MBB, MBBI, DL, TII->get(RISCV::ADDI), SPReg) can be eliminated. Firstly, the value of calleeSavedStackSize can be regarded as a aligned value(For example, aligned to MFI.getStackAlign()). Then we can calculate the padding size by the aligned calleeSavedStackSize minus the original calleeSavedStackSize. When emits prologue, we can minus the value of
MFI.getStackSize() - original calleeSavedStackSize + aligned calleeSavedStackSize. When get the offset of the rvv object, we can MFI.getStackSize() - original calleesavedStackSize, because we just want to calculate the
non-calleesaved field size. My English is poor and I am a beginner of LLVM-RISCV. So I don't know if it makes sense to you.
Mar 13 2021
rebase
Mar 12 2021
Address @rogfer01 's comment.
Mar 5 2021
Fix comment error.
Pre-commit local-stack-allocation.ll test.
Mar 3 2021
Delete white spaces.
Address @rogfer01 's comment. Add rvv-framelayout.ll test.
Mar 1 2021
Address @luismarques 's comment
Feb 27 2021
delete unnecessary white space
Address @jrtc27 's comments
Feb 25 2021
Ping.
Feb 24 2021
Address @rogfer01 's comments.
Feb 23 2021
Feb 22 2021
address @HsiangKai and @rogfer01 's comments
Feb 21 2021
Feb 20 2021
Feb 19 2021
add test cases that deleted incautious
address @criag.topper 's comment
Feb 17 2021
Feb 12 2021
Ping.
Feb 11 2021
Address @craig.topper 's comments
Address craig.topper 's comment
Address craig.topper 's comment
ping.
Feb 7 2021
Feb 6 2021
Feb 5 2021
According to @jrtc27 's review that is
"As for Zfinx itself, well, the idea is fine, but I really detest the way it's being done as an extension to F/D/Zfh. Running F code on an FZfh core _does not work_ so it is not an _extension_. Instead it should really be a set of separate extensions to I/E that conflict with F/D/Zfh, i.e. Zfinx, Zdinx and Zfhinx, but apparently asking code that complies with a ratified standard to change itself in order to not break when a new extension is introduced is a-ok in the RISC-V world.".
We split the Zfinx into 3 separate extensions which is Zfinx, Zdinx, and Zfhinx.
Jan 24 2021
Address craig.topper's comment.
Jan 22 2021
Get it.
Jan 21 2021
ping...
Jan 4 2021
Dec 28 2020
Are you have plans to promote the codegen of rv32e, if not, I want to try it