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.

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

Intrinsic function naming scheme #18

Open
kito-cheng opened this issue Apr 1, 2021 · 0 comments
Open

Intrinsic function naming scheme #18

kito-cheng opened this issue Apr 1, 2021 · 0 comments

Comments

@kito-cheng
Copy link
Collaborator

There is many extension has propose to add their own intrinsic function, like V, B, K and P.

And all of those extension are using slight different naming scheme:

K and B using same naming scheme:

_rv_<opname> for XLEN sensitive operations. 
_rv32_<opname> for 32-bits operation 
_rv64_<opname> for 64-bits operation 

P's naming scheme is just using __rv__ as prefix, and also provide GNU SIMD vector extension version with prefix __rv__v_<opname>

__rv__<opname> for scalar operation and SIMD operation in XLEN unsigned integer version.
__rv__v_<opname> for SIMD operation

V's naming scheme is quite different than others, it didn't use __ as prefix, but I think intrinsic for vector it more like a language extension.

v<opname>

I think it would be great if we have consistent intrinsic function naming scheme for all extension.
I don't have strong opinions here, but I think create an issue to gather feedback and raise discussion here would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant