Russ Cox <******@****.***> 1638378945 -0500

pkg syscall (freebsd-riscv64), const SYS_SCTP_GENERIC_RECVMSG = 474 #53466
pkg syscall (freebsd-riscv64), const SYS_SCTP_GENERIC_RECVMSG ideal-int #53466
pkg syscall (freebsd-riscv64), const SYS_SCTP_GENERIC_SENDMSG = 472 #53466
pkg syscall (freebsd-riscv64), const SYS_SCTP_GENERIC_SENDMSG ideal-int #53466
pkg syscall (freebsd-riscv64), const SYS_SCTP_GENERIC_SENDMSG_IOV = 473 #53466

see https://golang.org/pkg/go/build/#hdr-Build_Constraints).

When cross-compiling, you must specify a C cross-compiler for cgo to
use. You can do this by setting the generic CC_FOR_TARGET or the
more specific CC_FOR_${GOOS}_${GOARCH} (for example, CC_FOR_linux_arm)
environment variable when building the toolchain using make.bash,
or you can set the CC environment variable any time you run the go tool.

what the toolchain actually generates for that operation might
not be a move instruction at all, perhaps a clear or load.
Or it might correspond exactly to the machine instruction with that name.
In general, machine-specific operations tend to appear as themselves, while more general concepts like
memory move and subroutine call and return are more abstract.
The details vary with architecture, and we apologize for the imprecision; the situation is not well-defined.
</p>

	{"3-4", 3 - 4, true},
	{"2|5", 2 | 5, true},
	{"3^4", 3 ^ 4, true},
	{"3*4", 3 * 4, true},
	{"14/4", 14 / 4, true},
	{"3<<4", 3 << 4, true},
	{"48>>3", 48 >> 3, true},
	{"3&9", 3 & 9, true},
	// General
	{"3*2+3", 3*2 + 3, true},
	{"3+2*3", 3 + 2*3, true},
	{"3*(2+3)", 3 * (2 + 3), true},
	{"3*-(2+3)", 3 * -(2 + 3), true},
	{"3<<2+4", 3<<2 + 4, true},
	{"3<<2+4", 3<<2 + 4, true},
	{"3<<(2+4)", 3 << (2 + 4), true},

	}

	// Apply overrides.
	for old, new := range override {
		if id := goIdent[old]; id != nil {
			id.Name = new
		}
	}

	// Any names still using the _C syntax are not going to compile,
	// although in general we don't know whether they all made it
	// into the file, so we can't warn here.
	//
	// The most common case is union types, which begin with
	// _Ctype_union and for which typedef[name] is a Go byte

		register[name] = int16(i)
	}
	for i := riscv.REG_F0; i <= riscv.REG_F31; i++ {
		name := fmt.Sprintf("F%d", i-riscv.REG_F0)
		register[name] = int16(i)
	}

	// General registers with ABI names.
	register["ZERO"] = riscv.REG_ZERO
	register["RA"] = riscv.REG_RA
	register["SP"] = riscv.REG_SP
	register["GP"] = riscv.REG_GP
	register["TP"] = riscv.REG_TP
	register["T0"] = riscv.REG_T0

language version 1.17, in October 2021, before the introduction of generics.
It is provided for historical interest.
The current reference manual can be found <a href="/doc/go_spec.html">here</a>.
For more information and other documents, see <a href="/">go.dev</a>.
</p>

<p>
Go is a general-purpose language designed with systems programming

Type equations are always solved for the bound type parameters only.
</p>

<p>
Type inference supports calls of generic functions and assignments
of generic functions to (explicitly function-typed) variables.
This includes passing generic functions as arguments to other
(possibly also generic) functions, and returning generic functions
as results.
Type inference operates on a set of equations specific to each of
these cases.

pkg syscall (freebsd-arm64), const SYS_SCTP_GENERIC_RECVMSG = 474
pkg syscall (freebsd-arm64), const SYS_SCTP_GENERIC_RECVMSG ideal-int
pkg syscall (freebsd-arm64), const SYS_SCTP_GENERIC_SENDMSG = 472
pkg syscall (freebsd-arm64), const SYS_SCTP_GENERIC_SENDMSG ideal-int
pkg syscall (freebsd-arm64), const SYS_SCTP_GENERIC_SENDMSG_IOV = 473
pkg syscall (freebsd-arm64), const SYS_SCTP_GENERIC_SENDMSG_IOV ideal-int