Review multilibs being used for gcc #1186
Comments
|
My understanding is that multilib relates to builds of the standard libraries. I don’t think any of C standard libraries depend on crypto or Zifencei, and they probably work well enough without bit manipulation. I’m inclined to leave this as it is, and a user with special requirements can customize their libraries.
It also isn’t clear that building with Zb* does anything right now.
riscv-collab/riscv-gnu-toolchain#1354
James knows more GCC than me and might have other ideas.
David
… On Dec 9, 2024, at 3:18 PM, Jordan Carlin ***@***.***> wrote:
Right now we are building the following multilibs for gcc:
rv32e-ilp32e
rv32i-ilp32
rv32im-ilp32
rv32iac-ilp32
rv32imac-ilp32
rv32imafc-ilp32f
rv32imafdc-ilp32d
rv64i-lp64
rv64ic-lp64
rv64iac-lp64
rv64imac-lp64
rv64imafdc-lp64d
rv64im-lp64
Notably absent is anything related to bit manipulation, crypto, zifencei, and zfh, but many other extensions that we use are also missing. It is probably worth reviewing these and at least adding multilib configurations that match each of the main CVW configs.
—
Reply to this email directly, view it on GitHub <#1186>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR4AA3Z4YFGSOUC75REUOVT2EYQNFAVCNFSM6AAAAABTJ4TRIGVHI2DSMVQWIX3LMV43ASLTON2WKOZSG4ZDQNJQGA2TOMI>.
You are receiving this because you are subscribed to this thread.
|
|
@stineje Any opinions/insight regarding multilibs? Otherwise I'm fine leaving as it is for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now we are building the following multilibs for gcc:
Notably absent is anything related to bit manipulation, crypto, zifencei, and zfh, but many other extensions that we use are also missing. It is probably worth reviewing these and at least adding multilib configurations that match each of the main CVW configs.
The text was updated successfully, but these errors were encountered: