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
{{ message }}
This repository has been archived by the owner on Sep 19, 2024. It is now read-only.
After having a look at the initial proposal, i was wondering if the choice of datatypes is decided or up for discussion. Currently, datatypes like int, unsigned long etc are being used. Those datatypes are not well defined in the standard (e.g. their length being just a minimum required), which is why industry specific software like Automotive mandates the use of datatypes with defined length like uint32_t etc.
I would also expect the use of size_t (32 bits for RV32, 64 for RV64). Thats totally ok.
Looking forward to hear your feedback.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After having a look at the initial proposal, i was wondering if the choice of datatypes is decided or up for discussion. Currently, datatypes like int, unsigned long etc are being used. Those datatypes are not well defined in the standard (e.g. their length being just a minimum required), which is why industry specific software like Automotive mandates the use of datatypes with defined length like uint32_t etc.
I would also expect the use of size_t (32 bits for RV32, 64 for RV64). Thats totally ok.
Looking forward to hear your feedback.
The text was updated successfully, but these errors were encountered: