Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Why choose libraries based on riscv64-* or riscv32-**instead of xlen? #2

Open
majin2020 opened this issue Jul 31, 2023 · 1 comment
Open

Why choose libraries based on riscv64-* or riscv32-**instead of xlen? #2

majin2020 opened this issue Jul 31, 2023 · 1 comment

Comments

@majin2020
Copy link

I found that when I use the compiler riscv64, no matter -march = rv32gc or -march = rv64gc, typedef signed long int64_t; always appears. Obviously, when -march = rv32gc, it is correct to typedef the signed long long int64_t;.
@kraj
Copy link
Owner

kraj commented Jul 31, 2023

yes, we can correct that, Care to send a patch ? RV32 port is still not upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kraj @majin2020