17 “C” Standard Extension for Compressed Instructions, Version 2.0
This chapter describes the current proposal for the RISC-V standard compressed instruction-set extension, named “C”, which reduces static and dynamic code size by adding short 16-bit instruction encodings for common operations. The C extension can be added to any of the base ISAs (RV32, RV64, RV128), and we use the generic term “RVC” to cover any of these. Typically, 50%–60% of the RISC-V instructions in a program can be replaced with RVC instructions, resulting in a 25%–30% code-size reduction.
17.1 Overview
RVC uses a simple compression scheme that offers shorter 16-bit versions of common 32-bit RISC-V instructions when:
the immediate or address offset is small, or
one of the registers is the zero register (x0), the
ABI link register (x1), or the ABI stack pointer ( x2), or
the destination register and the first source register are identical, or
the registers used are the 8 most popular ones.
The C extension is compatible with all other standard instruction extensions. The C extension allows 16-bit instructions to be freely intermixed with 32-bit instructions, with the latter now able to start on any 16-bit boundary, i.e., IALIGN=16. With the addition of the C extension, no instructions can raise instruction-address-misaligned exceptions.
The compressed instruction encodings are mostly common across RV32C, RV64C, and RV128C, but as shown in Table [rvcopcodemap], a few opcodes are used for different purposes depending on base ISA. For example, the wider address-space RV64C and RV128C variants require additional opcodes to compress loads and stores of 64-bit integer values, while RV32C uses the same opcodes to compress loads and stores of single-precision floating-point values. Similarly, RV128C requires additional opcodes to capture loads and stores of 128-bit integer values, while these same opcodes are used for loads and stores of double-precision floating-point values in RV32C and RV64C. If the C extension is implemented, the appropriate compressed floating-point load and store instructions must be provided whenever the relevant standard floating-point extension (F and/or D) is also implemented. In addition, RV32C includes a compressed jump and link instruction to compress short-range subroutine calls, where the same opcode is used to compress ADDIW for RV64C and RV128C.
Double-precision loads and stores are a significant fraction of static and dynamic instructions, hence the motivation to include them in the RV32C and RV64C encoding.
Although single-precision loads and stores are not a significant source of static or dynamic compression for benchmarks compiled for the currently supported ABIs, for microcontrollers that only provide hardware single-precision floating-point units and have an ABI that only supports single-precision floating-point numbers, the single-precision loads and stores will be used at least as frequently as double-precision loads and stores in the measured benchmarks. Hence, the motivation to provide compressed support for these in RV32C.
Short-range subroutine calls are more likely in small binaries for microcontrollers, hence the motivation to include these in RV32C.
Although reusing opcodes for different purposes for different base ISAs adds some complexity to documentation, the impact on implementation complexity is small even for designs that support multiple base ISAs. The compressed floating-point load and store variants use the same instruction format with the same register specifiers as the wider integer loads and stores.
RVC was designed under the constraint that each RVC instruction expands into a single 32-bit instruction in either the base ISA (RV32I/E, RV64I, or RV128I) or the F and D standard extensions where present. Adopting this constraint has two main benefits:
Hardware designs can simply expand RVC instructions during decode, simplifying verification and minimizing modifications to existing microarchitectures.
Compilers can be unaware of the RVC extension and leave code compression to the assembler and linker, although a compression-aware compiler will generally be able to produce better results.
We felt the multiple complexity reductions of a simple one-one mapping between C and base IFD instructions far outweighed the potential gains of a slightly denser encoding that added additional instructions only supported in the C extension, or that allowed encoding of multiple IFD instructions in one C instruction.
It is important to note that the C extension is not designed to be a stand-alone ISA, and is meant to be used alongside a base ISA.
Variable-length instruction sets have long been used to improve code density. For example, the IBM Stretch [stretch], developed in the late 1950s, had an ISA with 32-bit and 64-bit instructions, where some of the 32-bit instructions were compressed versions of the full 64-bit instructions. Stretch also employed the concept of limiting the set of registers that were addressable in some of the shorter instruction formats, with short branch instructions that could only refer to one of the index registers. The later IBM 360 architecture [ibm360] supported a simple variable-length instruction encoding with 16-bit, 32-bit, or 48-bit instruction formats.
In 1963, CDC introduced the Cray-designed CDC 6600 [cdc6600], a precursor to RISC architectures, that introduced a register-rich load-store architecture with instructions of two lengths, 15-bits and 30-bits. The later Cray-1 design used a very similar instruction format, with 16-bit and 32-bit instruction lengths.
The initial RISC ISAs from the 1980s all picked performance over code size, which was reasonable for a workstation environment, but not for embedded systems. Hence, both ARM and MIPS subsequently made versions of the ISAs that offered smaller code size by offering an alternative 16-bit wide instruction set instead of the standard 32-bit wide instructions. The compressed RISC ISAs reduced code size relative to their starting points by about 25–30%, yielding code that was significantly smaller than 80x86. This result surprised some, as their intuition was that the variable-length CISC ISA should be smaller than RISC ISAs that offered only 16-bit and 32-bit formats.
Since the original RISC ISAs did not leave sufficient opcode space free to include these unplanned compressed instructions, they were instead developed as complete new ISAs. This meant compilers needed different code generators for the separate compressed ISAs. The first compressed RISC ISA extensions (e.g., ARM Thumb and MIPS16) used only a fixed 16-bit instruction size, which gave good reductions in static code size but caused an increase in dynamic instruction count, which led to lower performance compared to the original fixed-width 32-bit instruction size. This led to the development of a second generation of compressed RISC ISA designs with mixed 16-bit and 32-bit instruction lengths (e.g., ARM Thumb2, microMIPS, PowerPC VLE), so that performance was similar to pure 32-bit instructions but with significant code size savings. Unfortunately, these different generations of compressed ISAs are incompatible with each other and with the original uncompressed ISA, leading to significant complexity in documentation, implementations, and software tools support.
Of the commonly used 64-bit ISAs, only PowerPC and microMIPS currently supports a compressed instruction format. It is surprising that the most popular 64-bit ISA for mobile platforms (ARM v8) does not include a compressed instruction format given that static code size and dynamic instruction fetch bandwidth are important metrics. Although static code size is not a major concern in larger systems, instruction fetch bandwidth can be a major bottleneck in servers running commercial workloads, which often have a large instruction working set.
Benefiting from 25 years of hindsight, RISC-V was designed to support compressed instructions from the outset, leaving enough opcode space for RVC to be added as a simple extension on top of the base ISA (along with many other extensions). The philosophy of RVC is to reduce code size for embedded applications and to improve performance and energy-efficiency for all applications due to fewer misses in the instruction cache. Waterman shows that RVC fetches 25%-30% fewer instruction bits, which reduces instruction cache misses by 20%-25%, or roughly the same performance impact as doubling the instruction cache size [waterman-ms].
17.2 Compressed Instruction Formats
Table 1.1 shows the nine compressed instruction
formats. CR, CI, and CSS can use any of the 32 RVI registers, but CIW,
CL, CS, CA, and CB are limited to just 8 of them. Table [registers]
lists these popular registers, which correspond to registers x8
to x15. Note that there is a
separate version of load and store instructions that use the stack
pointer as the base address register, since saving to and restoring
from the stack are so prevalent, and that they use the CI and CSS
formats to allow access to all 32 data registers. CIW supplies an
8-bit immediate for the ADDI4SPN instruction.
The RISC-V ABI was changed to make the frequently used registers map
to registers x8–x15. This simplifies the decompression
decoder by having a contiguous naturally aligned set of register
numbers, and is also compatible with the RV32E base ISA,
which only has 16 integer registers.
Compressed register-based floating-point loads and stores also use the
CL and CS formats respectively, with the eight registers mapping to
f8 to f15.
The standard RISC-V calling convention maps the most frequently used
floating-point registers to registers f8 to f15, which
allows the same register decompression decoding as for integer
register numbers.
The formats were designed to keep bits for the two register source specifiers in the same place in all instructions, while the destination register field can move. When the full 5-bit destination register specifier is present, it is in the same place as in the 32-bit RISC-V encoding. Where immediates are sign-extended, the sign-extension is always from bit 12. Immediate fields have been scrambled, as in the base specification, to reduce the number of immediate muxes required.
The immediate fields are scrambled in the instruction formats instead of in sequential order so that as many bits as possible are in the same position in every instruction, thereby simplifying implementations.
For many RVC instructions, zero-valued immediates are disallowed and
x0 is not a valid 5-bit register specifier. These restrictions
free up encoding space for other instructions requiring fewer operand
bits.
| RVC Register Number | 000 | 001 | 010 | 011 | 100 | 101 | 110 | 111 |
| Integer Register Number | x8 |
x9 |
x10 |
x11 |
x12 |
x13 |
x14 |
x15 |
| Integer Register ABI Name | s0 |
s1 |
a0 |
a1 |
a2 |
a3 |
a4 |
a5 |
| Floating-Point Register Number | f8 |
f9 |
f10 |
f11 |
f12 |
f13 |
f14 |
f15 |
| Floating-Point Register ABI Name | fs0 |
fs1 |
fa0 |
fa1 |
fa2 |
fa3 |
fa4 |
fa5 |
17.3 Load and Store Instructions
To increase the reach of 16-bit instructions, data-transfer instructions use zero-extended immediates that are scaled by the size of the data in bytes: ×4 for words, ×8 for double words, and ×16 for quad words.
RVC provides two variants of loads and stores. One uses the ABI stack
pointer, x2, as the base address and can target any data register. The
other can reference one of 8 base address registers and one of 8 data
registers.
Stack-Pointer-Based Loads and Stores
These instructions use the CI format.
C.LWSP loads a 32-bit value from memory into register rd. It computes
an effective address by adding the zero-extended offset, scaled by 4, to
the stack pointer, x2. It expands to lw rd, offset(x2).
C.LWSP is only valid when rd ≠ x0;
the code points with rd = x0 are reserved.
C.LDSP is an RV64C/RV128C-only instruction that loads a 64-bit value from memory into
register rd. It computes its effective address by adding the
zero-extended offset, scaled by 8, to the stack pointer, x2.
It expands to ld rd, offset(x2).
C.LDSP is only valid when rd ≠ x0;
the code points with rd = x0 are reserved.
C.LQSP is an RV128C-only instruction that loads a 128-bit value from memory
into register rd. It computes its effective address by adding the
zero-extended offset, scaled by 16, to the stack pointer, x2.
It expands to lq rd, offset(x2).
C.LQSP is only valid when rd ≠ x0;
the code points with rd = x0 are reserved.
C.FLWSP is an RV32FC-only instruction that loads a single-precision
floating-point value from memory into floating-point register rd. It
computes its effective address by adding the zero-extended offset,
scaled by 4, to the stack pointer, x2. It expands to flw rd, offset(x2).
C.FLDSP is an RV32DC/RV64DC-only instruction that loads a double-precision
floating-point value from memory into floating-point register rd. It
computes its effective address by adding the zero-extended offset,
scaled by 8, to the stack pointer, x2. It expands to fld rd, offset(x2).
These instructions use the CSS format.
C.SWSP stores a 32-bit value in register rs2 to memory. It computes
an effective address by adding the zero-extended offset, scaled by 4, to
the stack pointer, x2.
It expands to sw rs2, offset(x2).
C.SDSP is an RV64C/RV128C-only instruction that stores a 64-bit value in register
rs2 to memory. It computes an effective address by adding the
zero-extended offset, scaled by 8, to the stack pointer, x2.
It expands to sd rs2, offset(x2).
C.SQSP is an RV128C-only instruction that stores a 128-bit value in register
rs2 to memory. It computes an effective address by adding the
zero-extended offset, scaled by 16, to the stack pointer, x2.
It expands to sq rs2, offset(x2).
C.FSWSP is an RV32FC-only instruction that stores a single-precision
floating-point value in floating-point register rs2 to memory. It
computes an effective address by adding the zero-extended offset, scaled
by 4, to the stack pointer, x2. It expands to fsw rs2, offset(x2).
C.FSDSP is an RV32DC/RV64DC-only instruction that stores a double-precision
floating-point value in floating-point register rs2 to memory. It
computes an effective address by adding the zero-extended offset, scaled
by 8, to the stack pointer, x2. It expands to fsd rs2, offset(x2).
Register save/restore code at function entry/exit represents a significant portion of static code size. The stack-pointer-based compressed loads and stores in RVC are effective at reducing the save/restore static code size by a factor of 2 while improving performance by reducing dynamic instruction bandwidth.
A common mechanism used in other ISAs to further reduce save/restore code size is load-multiple and store-multiple instructions. We considered adopting these for RISC-V but noted the following drawbacks to these instructions:
These instructions complicate processor implementations.
For virtual memory systems, some data accesses could be resident in physical memory and some could not, which requires a new restart mechanism for partially executed instructions.
Unlike the rest of the RVC instructions, there is no IFD equivalent to Load Multiple and Store Multiple.
Unlike the rest of the RVC instructions, the compiler would have to be aware of these instructions to both generate the instructions and to allocate registers in an order to maximize the chances of the them being saved and stored, since they would be saved and restored in sequential order.
Simple microarchitectural implementations will constrain how other instructions can be scheduled around the load and store multiple instructions, leading to a potential performance loss.
The desire for sequential register allocation might conflict with the featured registers selected for the CIW, CL, CS, CA, and CB formats.
Furthermore, much of the gains can be realized in software by replacing prologue and epilogue code with subroutine calls to common prologue and epilogue code, a technique described in Section 5.6 of [waterman-phd].
While reasonable architects might come to different conclusions, we decided to omit load and store multiple and instead use the software-only approach of calling save/restore millicode routines to attain the greatest code size reduction.
Register-Based Loads and Stores
These instructions use the CL format.
C.LW loads a 32-bit value from memory into register rd ′. It computes
an effective address by adding the zero-extended offset, scaled by 4, to
the base address in register rs1 ′.
It expands to lw rd ', offset(rs1 ').
C.LD is an RV64C/RV128C-only instruction that loads a 64-bit value from memory into
register rd ′. It computes an effective address by adding the
zero-extended offset, scaled by 8, to the base address in register
rs1 ′.
It expands to ld rd ', offset(rs1 ').
C.LQ is an RV128C-only instruction that loads a 128-bit value from memory into
register rd ′. It computes an effective address by adding the
zero-extended offset, scaled by 16, to the base address in register
rs1 ′.
It expands to lq rd ', offset(rs1 ').
C.FLW is an RV32FC-only instruction that loads a single-precision
floating-point value from memory into floating-point register rd ′. It
computes an effective address by adding the zero-extended offset, scaled
by 4, to the base address in register rs1 ′. It expands to flw rd ', offset(rs1 ').
C.FLD is an RV32DC/RV64DC-only instruction that loads a double-precision
floating-point value from memory into floating-point register rd ′. It
computes an effective address by adding the zero-extended offset, scaled
by 8, to the base address in register rs1 ′. It expands to fld rd ', offset(rs1 ').
These instructions use the CS format.
C.SW stores a 32-bit value in register rs2 ′ to memory. It computes an
effective address by adding the zero-extended offset, scaled by 4, to
the base address in register rs1 ′.
It expands to sw rs2 ', offset(rs1 ').
C.SD is an RV64C/RV128C-only instruction that stores a 64-bit value in
register rs2 ′ to memory. It computes an effective address by adding
the zero-extended offset, scaled by 8, to the base address in register
rs1 ′.
It expands to sd rs2 ', offset(rs1 ').
C.SQ is an RV128C-only instruction that stores a 128-bit value in register
rs2 ′ to memory. It computes an effective address by adding the
zero-extended offset, scaled by 16, to the base address in register
rs1 ′.
It expands to sq rs2 ', offset(rs1 ').
C.FSW is an RV32FC-only instruction that stores a single-precision
floating-point value in floating-point register rs2 ′ to memory. It
computes an effective address by adding the zero-extended offset, scaled
by 4, to the base address in register rs1 ′. It expands to fsw rs2 ', offset(rs1 ').
C.FSD is an RV32DC/RV64DC-only instruction that stores a double-precision
floating-point value in floating-point register rs2 ′ to memory. It
computes an effective address by adding the zero-extended offset, scaled
by 8, to the base address in register rs1 ′. It expands to fsd rs2 ', offset(rs1 ').
17.4 Control Transfer Instructions
RVC provides unconditional jump instructions and conditional branch instructions. As with base RVI instructions, the offsets of all RVC control transfer instruction are in multiples of 2 bytes.
These instructions use the CJ format.
C.J performs an unconditional control transfer. The offset is sign-extended and
added to the pc to form the jump target address. C.J can therefore target
a ±2 KiB range. C.J expands to jal x0, offset.
C.JAL is an RV32C-only instruction that performs the same operation as C.J,
but additionally writes the address of the instruction following the jump
(pc+2) to the link register, x1. C.JAL expands to jal x1, offset.
These instructions use the CR format.
C.JR (jump register) performs an unconditional control transfer to
the address in register rs1. C.JR expands to jalr x0, 0(rs1).
C.JR is only valid when rs1 ≠ x0; the code point
with rs1 = x0 is reserved.
C.JALR (jump and link register) performs the same operation as C.JR,
but additionally writes the address of the instruction following the
jump (pc+2) to the link register, x1. C.JALR expands to
jalr x1, 0(rs1).
C.JALR is only valid when rs1 ≠ x0; the code point
with rs1 = x0 corresponds to the C.EBREAK instruction.
Strictly speaking, C.JALR does not expand exactly to a base RVI instruction as the value added to the PC to form the link address is 2 rather than 4 as in the base ISA, but supporting both offsets of 2 and 4 bytes is only a very minor change to the base microarchitecture.
These instructions use the CB format.
C.BEQZ performs conditional control transfers. The offset is sign-extended
and added to the pc to form the branch target address. It can
therefore target a ±256 B range. C.BEQZ takes the branch if the
value in register rs1 ′ is zero. It expands to beq rs1 ', x0, offset.
C.BNEZ is defined analogously, but it takes the branch if rs1 ′ contains
a nonzero value. It expands to bne rs1 ', x0, offset.
17.5 Integer Computational Instructions
RVC provides several instructions for integer arithmetic and constant generation.
Integer Constant-Generation Instructions
The two constant-generation instructions both use the CI instruction format and can target any integer register.
C.LI loads the sign-extended 6-bit immediate, imm, into
register rd.
C.LI expands into addi rd, x0, imm.
C.LI is only valid when rd≠x0;
the code points with rd=x0 encode HINTs.
C.LUI loads the non-zero 6-bit immediate field into bits 17–12 of the
destination register, clears the bottom 12 bits, and sign-extends bit
17 into all higher bits of the destination.
C.LUI expands into lui rd, nzimm.
C.LUI is only valid when
rd ≠ {x0,x2},
and when the immediate is not equal to zero.
The code points with nzimm=0 are reserved; the remaining code points
with rd=x0 are HINTs; and the remaining code points with
rd=x2 correspond to the C.ADDI16SP instruction.
Integer Register-Immediate Operations
These integer register-immediate operations are encoded in the CI format and perform operations on an integer register and a 6-bit immediate.
C.ADDI adds the non-zero sign-extended 6-bit immediate to the value in
register rd then writes the result to rd. C.ADDI expands
into addi rd, rd, nzimm.
C.ADDI is only valid when rd≠x0 and nzimm≠0.
The code points with rd=x0 encode the C.NOP instruction;
the remaining code points with nzimm=0 encode HINTs.
C.ADDIW is an RV64C/RV128C-only instruction that performs the same
computation but produces a 32-bit result, then sign-extends result to
64 bits. C.ADDIW expands into addiw rd, rd, imm. The
immediate can be zero for C.ADDIW, where this corresponds to sext.w rd. C.ADDIW is only valid when rd≠x0;
the code points with rd=x0 are reserved.
C.ADDI16SP shares the opcode with C.LUI, but has a destination field
of x2. C.ADDI16SP adds the non-zero sign-extended 6-bit immediate to
the value in the stack pointer (sp=x2), where the
immediate is scaled to represent multiples of 16 in the range
(-512,496). C.ADDI16SP is used to adjust the stack pointer in procedure
prologues and epilogues. It expands into addi x2, x2, nzimm.
C.ADDI16SP is only valid when nzimm≠0;
the code point with nzimm=0 is reserved.
In the standard RISC-V calling convention, the stack pointer sp
is always 16-byte aligned.
C.ADDI4SPN is a CIW-format instruction that adds a zero-extended
non-zero immediate, scaled by 4, to the stack pointer, x2, and
writes the result to rd '. This instruction is used
to generate pointers to stack-allocated variables, and expands to
addi rd ', x2, nzuimm.
C.ADDI4SPN is only valid when nzuimm≠0;
the code points with nzuimm=0 are reserved.
C.SLLI is a CI-format instruction that performs a logical left shift
of the value in register rd then writes the result to rd.
The shift amount is encoded in the shamt field.
For RV128C, a shift amount of zero is used to encode a shift of 64.
C.SLLI expands into slli rd, rd, shamt, except for
RV128C with shamt=0, which expands to slli rd, rd, 64.
For RV32C, shamt[5] must be zero; the code points with shamt[5]=1
are designated for custom extensions. For RV32C and RV64C, the shift
amount must be non-zero; the code points with shamt=0 are HINTs. For
all base ISAs, the code points with rd=x0 are HINTs, except those
with shamt[5]=1 in RV32C.
C.SRLI is a CB-format instruction that performs a logical right shift
of the value in register rd ′ then writes the result to rd ′.
The shift amount is encoded in the shamt field.
For RV128C, a shift amount of zero is used to encode a shift of 64.
Furthermore, the shift amount is sign-extended
for RV128C, and so the legal shift amounts are 1–31, 64, and 96–127.
C.SRLI expands into srli rd ', rd ', shamt,
except for RV128C with shamt=0, which expands to
srli rd ', rd ', 64.
For RV32C, shamt[5] must be zero; the code points with shamt[5]=1 are designated for custom extensions. For RV32C and RV64C, the shift amount must be non-zero; the code points with shamt=0 are HINTs.
C.SRAI is defined analogously to C.SRLI, but instead performs an arithmetic
right shift.
C.SRAI expands to srai rd ', rd ', shamt.
Left shifts are usually more frequent than right shifts, as left shifts are frequently used to scale address values. Right shifts have therefore been granted less encoding space and are placed in an encoding quadrant where all other immediates are sign-extended. For RV128, the decision was made to have the 6-bit shift-amount immediate also be sign-extended. Apart from reducing the decode complexity, we believe right-shift amounts of 96–127 will be more useful than 64–95, to allow extraction of tags located in the high portions of 128-bit address pointers. We note that RV128C will not be frozen at the same point as RV32C and RV64C, to allow evaluation of typical usage of 128-bit address-space codes.
C.ANDI is a CB-format instruction that computes the bitwise AND of
the value in register rd ′ and the sign-extended 6-bit immediate,
then writes the result to rd ′.
C.ANDI expands to andi rd ', rd ', imm.
Integer Register-Register Operations
These instructions use the CR format.
C.MV copies the value in register rs2 into register rd. C.MV
expands into add rd, x0, rs2.
C.MV is only valid when rs2 ≠ x0; the code points
with rs2 = x0 correspond to the C.JR instruction.
The code points with rs2 ≠ x0 and
rd = x0 are HINTs.
C.MV expands to a different instruction than the canonical MV pseudoinstruction, which instead uses ADDI. Implementations that handle MV specially, e.g. using register-renaming hardware, may find it more convenient to expand C.MV to MV instead of ADD, at slight additional hardware cost.
C.ADD adds the values in registers rd and rs2 and writes the
result to register rd. C.ADD expands into add rd, rd, rs2.
C.ADD is only valid when rs2 ≠ x0; the code points
with rs2 = x0 correspond to the C.JALR and C.EBREAK instructions.
The code points with rs2 ≠ x0 and
rd = x0 are HINTs.
These instructions use the CA format.
C.AND computes the bitwise AND of the values in registers rd ′
and rs2 ′, then writes the result to register rd ′.
C.AND expands into and rd ', rd ', rs2 '.
C.OR computes the bitwise OR of the values in registers rd ′
and rs2 ′, then writes the result to register rd ′.
C.OR expands into or rd ', rd ', rs2 '.
C.XOR computes the bitwise XOR of the values in registers rd ′
and rs2 ′, then writes the result to register rd ′.
C.XOR expands into xor rd ', rd ', rs2 '.
C.SUB subtracts the value in register rs2 ′ from the value in
register rd ′, then writes the result to register rd ′.
C.SUB expands into sub rd ', rd ', rs2 '.
C.ADDW is an RV64C/RV128C-only instruction that adds the values in
registers rd ′ and rs2 ′, then sign-extends the lower
32 bits of the sum before writing the result to register rd ′.
C.ADDW expands into addw rd ', rd ', rs2 '.
C.SUBW is an RV64C/RV128C-only instruction that subtracts the value in
register rs2 ′ from the value in register rd ′, then
sign-extends the lower 32 bits of the difference before writing the result
to register rd ′. C.SUBW expands into subw rd ', rd ', rs2 '.
This group of six instructions do not provide large savings individually, but do not occupy much encoding space and are straightforward to implement, and as a group provide a worthwhile improvement in static and dynamic compression.
Defined Illegal Instruction
A 16-bit instruction with all bits zero is permanently reserved as an illegal instruction.
We reserve all-zero instructions to be illegal instructions to help trap attempts to execute zero-ed or non-existent portions of the memory space. The all-zero value should not be redefined in any non-standard extension. Similarly, we reserve instructions with all bits set to 1 (corresponding to very long instructions in the RISC-V variable-length encoding scheme) as illegal to capture another common value seen in non-existent memory regions.
NOP Instruction
C.NOP is a CI-format instruction that does not change any user-visible state,
except for advancing the pc and incrementing any applicable performance
counters. C.NOP expands to nop. C.NOP is only valid when imm=0;
the code points with imm≠0 encode HINTs.
Breakpoint Instruction
Debuggers can use the C.EBREAK instruction, which expands to ebreak,
to cause control to be transferred back to the debugging environment.
C.EBREAK shares the opcode with the C.ADD instruction, but with
rd and rs2 both zero, thus can also use the CR format.
17.6 Usage of C Instructions in LR/SC Sequences
On implementations that support the C extension, compressed forms of the I instructions permitted inside constrained LR/SC sequences, as described in Section [sec:lrscseq], are also permitted inside constrained LR/SC sequences.
The implication is that any implementation that claims to support both the A and C extensions must ensure that LR/SC sequences containing valid C instructions will eventually complete.
17.7 HINT Instructions
A portion of the RVC encoding space is reserved for microarchitectural HINTs.
Like the HINTs in the RV32I base ISA (see Section [sec:rv32i-hints]),
these instructions do not modify any architectural state, except for advancing
the pc and any applicable performance counters. HINTs are
executed as no-ops on implementations that ignore them.
RVC HINTs are encoded as computational instructions that do not modify the
architectural state, either because rd=x0
(e.g. C.ADD x0, t0 ), or because rd is overwritten
with a copy of itself (e.g. C.ADDI t0, 0 ).
This HINT encoding has been chosen so that simple implementations can ignore HINTs altogether, and instead execute a HINT as a regular computational instruction that happens not to mutate the architectural state.
RVC HINTs do not necessarily expand to their RVI HINT counterparts. For example, C.ADD x0, t0 might not encode the same HINT as ADD x0, x0, t0 .
The primary reason to not require an RVC HINT to expand to an RVI HINT is that HINTs are unlikely to be compressible in the same manner as the underlying computational instruction. Also, decoupling the RVC and RVI HINT mappings allows the scarce RVC HINT space to be allocated to the most popular HINTs, and in particular, to HINTs that are amenable to macro-op fusion.
Table 1.2 lists all RVC HINT code points. For RV32C, 78% of the HINT space is reserved for standard HINTs, but none are presently defined. The remainder of the HINT space is designated for custom HINTs; no standard HINTs will ever be defined in this subspace.
17.8 RVC Instruction Set Listings
Table [rvcopcodemap] shows a map of the major opcodes for RVC. Each row of the table corresponds to one quadrant of the encoding space. The last quadrant, which has the two least-significant bits set, corresponds to instructions wider than 16 bits, including those in the base ISAs. Several instructions are only valid for certain operands; when invalid, they are marked either RES to indicate that the opcode is reserved for future standard extensions; Custom to indicate that the opcode is designated for custom extensions; or HINT to indicate that the opcode is reserved for microarchitectural hints (see Section 1.7).
Tables [rvc-instr-table0]–[rvc-instr-table2] list the RVC instructions. [rvc-instr-table]
Removing the 32-bit alignment constraint on the original 32-bit instructions allows significantly greater code density.