This is a special case of "stupid nonhuman friendly names considered harmful".
RISC-V, like any instruction set, as extension. The extensions need names. The current standard names are stupid and human unfriendly.
For example, I just now see email that talks about "working through the process to move Svnapot aka the former Zsn to public review". I am the guy who originated the RISC-V NAPOT proposal for large pages. *I* had to do a double take to parse Svnapot - but at least "NAPOT" appeared in there somewhere, after I mentally parsed Svanapot into S.v.napot, where S = system, v = virtual memory, ...
The earlier name Zsn, I could never remember - and, again, I contributed the term NAPOT to the virtual memory discussion.
Stupidly short and obscure names had friction. They waste mind share.
other RISC-V extension names include
Some of these you can guess about what they apply to.
Ag comment: have verbose and compact names
Z-atomic-memory-operations ==> Zam
and so on
Did I mention that 1 of the reasons given for short obscure extension names was that they needed to fit within 8 or whatever characters on the command line processor for compiler?