// requires special handling.
func IsRISCV64VTypeI(op obj.As) bool {
	return op == riscv.AVSETVLI || op == riscv.AVSETIVLI
}

// IsRISCV64CSRO reports whether the op is an instruction that uses
// CSR symbolic names and whether that instruction expects a register
// or an immediate source operand.
func IsRISCV64CSRO(op obj.As) (imm bool, ok bool) {
	switch op {
	case riscv.ACSRRCI, riscv.ACSRRSI, riscv.ACSRRWI:
		imm = true

// license that can be found in the LICENSE file.

TEXT errors(SB),$0
	CSRRC	(X10), CYCLE, X5		// ERROR "integer register or immediate expected for 1st operand"
	CSRRC	X0, TU, X5			// ERROR "unknown CSR"
	CSRRC	X0, CYCLE			// ERROR "missing CSR name"
	CSRRC	X0, CYCLE, (X10)		// ERROR "needs an integer register output"
	CSRRC	$-1, TIME, X15			// ERROR "immediate out of range 0 to 31"
	CSRRCI	$32, TIME, X15			// ERROR "immediate out of range 0 to 31"

					return
				}
				if a[1].Type != obj.TYPE_SPECIAL {
					p.errorf("invalid value for second operand to %s instruction, must be a CSR name", op)
					return
				}
				prog.AddRestSourceArgs([]obj.Addr{a[1]})
				prog.From = a[0]
				prog.To = a[2]
				break
			}
			prog.From = a[0]
			prog.Reg = p.getRegister(prog, op, &a[1])

        * requests for a TLS client certificate for any node are approved if the CSR creator has `create` permission on the `certificatesigningrequests` resource and `nodeclient` subresource in the `certificates.k8s.io` API group

- Kubeadm: deprecate the "--csr-only" and "--csr-dir" flags of the "kubeadm init phase certs" subcommands. Please use "kubeadm alpha certs generate-csr" instead. This new command allows you to generate new private keys and certificate signing requests for all the control-plane components, so that the certificates can be signed by an external...

- Remove the deprecated flags `--csr-only` and `--csr-dir` from `kubeadm certs renew`. Please use `kubeadm certs generate-csr` instead. ([#104796](https://github.com/kubernetes/kubernetes/pull/104796), [@RA489](https://github.com/RA489))

- Resolves an issue using `kubectl certificate approve/deny` against a server serving the v1 CSR API ([#91691](https://github.com/kubernetes/kubernetes/pull/91691), [@liggitt](https://github.com/liggitt)) [SIG Auth and CLI]

### Other (Cleanup or Flake)

        * requests for a TLS client certificate for any node are approved if the CSR creator has `create` permission on the `certificatesigningrequests` resource and `nodeclient` subresource in the `certificates.k8s.io` API group

	SRAW	$1, X6					// 1b531340

	// 4.3: Load and Store Instructions (RV64I)
	LD	(X5), X6				// 03b30200
	LD	4(X5), X6				// 03b34200
	SD	X5, (X6)				// 23305300
	SD	X5, 4(X6)				// 23325300

	// 7.1: CSR Instructions
	CSRRC	X0, CYCLE, X5				// f33200c0
	CSRRC	X0, CYCLE, X0				// 733000c0
	CSRRC	X10, CYCLE, X5				// f33205c0
	CSRRC	$2, TIME, X5				// f37211c0
	CSRRCI	$2, TIME, X5				// f37211c0

- Kubeadm: remove the deprecated `--csr-only` and `--csr-dir` flags from `kubeadm init phase certs`. Deprecate the same flags under `kubeadm certs renew`. In both the cases the command `kubeadm certs generate-csr` should be used instead. ([#102108](https://github.com/kubernetes/kubernetes/pull/102108), [@neolit123](https://github.com/neolit123))