You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been having some questions about RV32E support in LLVM+Clang. It's difficult to consider adding support as the RV32E instruction set extension itself isn't yet "frozen" and the ABI isn't fully documented. A little more documentation on the proposed ABI has been added recently (thanks!), but I thought it would be worth making an issue to track the work that still needs to be done.
As far as I can see, we need:
Syscall ABI for RV32E (Syscall ABI for RV32E #11). Discussion on that issue also mentions dynamic linking
An integer register convention table for RV32E.
Add an RV32E table to "Default ABIs and type sizes" (or else specify if RV32E is identical to RV32G). Are long long and doubles still 8-byte aligned? Is long double still 16 bytes?
Are there other issues that need to be addressed? Please note: I'm simply creating this issue to track what needs to be done, not to claim it - I'm not currently distributing or directly supporting RV32E IP myself.
The text was updated successfully, but these errors were encountered:
Add an RV32E table to "Default ABIs and type sizes" (or else specify if RV32E is identical to RV32G). Are long long and doubles still 8-byte aligned? Is long double still 16 bytes?
For this item, it seems all alignment can align to 4 byte is fine since stack is 4 byte align, any alignment greater than stack align seems meaningless.
I've been having some questions about RV32E support in LLVM+Clang. It's difficult to consider adding support as the RV32E instruction set extension itself isn't yet "frozen" and the ABI isn't fully documented. A little more documentation on the proposed ABI has been added recently (thanks!), but I thought it would be worth making an issue to track the work that still needs to be done.
As far as I can see, we need:
Are there other issues that need to be addressed? Please note: I'm simply creating this issue to track what needs to be done, not to claim it - I'm not currently distributing or directly supporting RV32E IP myself.
The text was updated successfully, but these errors were encountered: