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

Naming the RV32E ABI with -mabi #3

Open
asb opened this issue Oct 25, 2017 · 3 comments
Open

Naming the RV32E ABI with -mabi #3

asb opened this issue Oct 25, 2017 · 3 comments

Comments

@asb
Copy link
Contributor

asb commented Oct 25, 2017

Should the RV32E ABI be explicitly targeted using -mabi=ilp32e? This would seem consistent with the other supported ABIs having unique -mabi strings. Of course for RV32E, no other ABI string is valid.
@asb
Copy link
Contributor Author

asb commented Nov 15, 2017

@palmer-dabbelt, @kito-cheng - thoughts? -mabi=ilp32e makes a lot of sense to me.

@kito-cheng
Copy link
Collaborator

kito-cheng commented Nov 15, 2017 •
edited
Loading

Yeah, sounds good idea, I'll take gcc and binutils part.

@palmer-dabbelt
Copy link

I agree that we need some way for -march=rv32i to target the E ABI. -march=rv32i -mabi=ilp32e seems good to me.

This was referenced Nov 20, 2017
Merged
Merged
@TommyMurphyTM1234 TommyMurphyTM1234 mentioned this issue Jan 25, 2018
Closed
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
3 participants
@asb @palmer-dabbelt @kito-cheng