User Details
- User Since
- May 4 2016, 7:01 PM (245 w, 5 d)
Today
Add test cases for floating point types.
Add test cases for floating point types.
Add test cases for floating point types.
Add test cases for floating point types.
Yesterday
Ping. If we all agree to use builtin types to model RVV types, is there any other issues we need to address in this patch?
Sat, Jan 16
Rebase.
Rebase.
Rebase.
Rebase.
Fri, Jan 15
Thu, Jan 14
According to "9. Vector Memory Alignment Constraints" in V specification, change the alignment of RVV types to the element size.
Wed, Jan 13
Recover comments.
Refine debug info for RVV types.
LGTM.
LGTM.
@liaolucy RISC-V vector types are sizeless types. Sizeless is kind of characteristic for builtin types. If we use attribute to declare RISC-V vector types, the frontend does not know anything about it. I still think to define RISC-V vector types as builtin types is a better way.
Let's focus on D94465. If there is anyone oppose it, I could reactivate this commit.
I also think one direct memory access is better than two memory accesses. I abandoned D93750 first. If there is anyone oppose it, I could reactivate it.
LGTM.
Tue, Jan 12
Address @jrtc27's comments.
Mon, Jan 11
Sun, Jan 10
Fri, Jan 8
Thu, Jan 7
D89237 is a better way to go.
Wed, Jan 6
Address @craig.topper and @jrtc27's comments.
Tue, Jan 5
LGTM.
Sun, Jan 3
@lenary, is it reasonable to implement targetHandlesStackFrameRounding() and handle the alignment in RISCVFrameLowering.cpp?
To consider the frame handling in D93750, is it reasonable to load/store whole vector registers for mask types regardless which kind of mask types?
Ping.
Fri, Jan 1
Mon, Dec 28
LGTM.
Sun, Dec 27
Rebase on D93784.
Rebase on master.
Sat, Dec 26
Deal with the case when there are realignment objects and RVV objects on the stack at the same time.
LGTM
Fri, Dec 25
Address @craig.topper's comments.