Skip to content
This repository has been archived by the owner on Feb 29, 2024. It is now read-only.

consider opcode bits placement for future instructions #169

Closed
jnk0le opened this issue Jun 28, 2022 · 2 comments
Closed

consider opcode bits placement for future instructions #169

jnk0le opened this issue Jun 28, 2022 · 2 comments

Comments

@jnk0le
Copy link
Contributor

jnk0le commented Jun 28, 2022

as everything outside v0.70 got postponed, i think it's worth to note that some of the current compressed encodings may lead to awkward encoding of potential new instructions.

e.g. #158 there is potential encoding with immediate symmetrical to c.lui

but current load/stores occupy all combinations of bits [11:10] with bit 12 set to 0, which means that any new istructions have to fit next to c.sh or with bit 12 set to 1. 12th bit is also the only one used for sign extensions by other instructions.

@tariqkurd-repo
Copy link
Contributor

I'll only change encodings if the architecture review committee require it (also they set the encodings anyway)

@jnk0le
Copy link
Contributor Author

jnk0le commented Jul 14, 2022

Moving these three extensions to the frozen state should now just be a formality.

maybe should poke @aswaterman before its too late again.

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

No branches or pull requests

2 participants