### Timer changes

Go 1.23 makes two significant changes to the implementation of
[time.Timer] and [time.Ticker].

First, `Timer`s and `Ticker`s that are no longer referred to by the program
become eligible for garbage collection immediately, even if their
`Stop` methods have not been called.
Earlier versions of Go did not collect unstopped `Timer`s until after
they had fired and never collected unstopped `Ticker`s.

<code>R15</code> points to the stack frame and should typically only be accessed using the
virtual registers <code>SP</code> and <code>FP</code>.
</p>

<p>
Load- and store-multiple instructions operate on a range of registers.
The range of registers is specified by a start register and an end register.
For example, <code>LMG</code> <code>(R9),</code> <code>R5,</code> <code>R7</code> would load

// registers in []. There may be comma-separated ranges or individual
// registers, as in [R1,R3-R5] or [V1.S4, V2.S4, V3.S4, V4.S4].
// For ARM, only R0 through R15 may appear.
// For ARM64, V0 through V31 with arrangement may appear.
//
// For 386/AMD64 register list specifies 4VNNIW-style multi-source operand.
// For range of 4 elements, Intel manual uses "+3" notation, for example:
//

pkg syscall (freebsd-riscv64), const EPROTO Errno #53466
pkg syscall (freebsd-riscv64), const EPROTONOSUPPORT = 43 #53466
pkg syscall (freebsd-riscv64), const EPROTOTYPE = 41 #53466
pkg syscall (freebsd-riscv64), const ERANGE = 34 #53466
pkg syscall (freebsd-riscv64), const EREMOTE = 71 #53466
pkg syscall (freebsd-riscv64), const EROFS = 30 #53466
pkg syscall (freebsd-riscv64), const ERPCMISMATCH = 73 #53466

	V4FMADDPS (AX), [Z0-Z0], K1, Z7  // ERROR "invalid instruction"
	// Invalid ranges in REG_LIST (low > high).
	// TODO(quasilyte): improve error message (#21860).
	V4FMADDPS (AX), [Z4-Z0], K1, Z7  // ERROR "invalid instruction"
	V4FMADDPS (AX), [Z1-Z0], K1, Z7  // ERROR "invalid instruction"
	// Mismatching registers in a range.
	// TODO(quasilyte): improve error message (#21860).

	<li>the index <code>x</code> is <i>in range</i> if <code>0 &lt;= x &lt; len(a)</code>,
	    otherwise it is <i>out of range</i></li>
</ul>

<p>
For <code>a</code> of <a href="#Array_types">array type</a> <code>A</code>:
</p>
<ul>
	<li>a <a href="#Constants">constant</a> index must be in range</li>
	<li>if <code>x</code> is out of range at run time,

pkg syscall (darwin-386), const EPROTO = 100
pkg syscall (darwin-386), const EPROTONOSUPPORT = 43
pkg syscall (darwin-386), const EPROTOTYPE = 41
pkg syscall (darwin-386), const EPWROFF = 82
pkg syscall (darwin-386), const ERANGE = 34
pkg syscall (darwin-386), const EREMOTE = 71
pkg syscall (darwin-386), const EROFS = 30
pkg syscall (darwin-386), const ERPCMISMATCH = 73
pkg syscall (darwin-386), const ESHLIBVERS = 87

		_mp_alloc _C_int;
		_mp_size _C_int;
		_mp_d *_C_mp_limb_t;
	}
	type _C_mpz_t [1]_C___mpz_struct

and then replaces each occurrence of a type C.xxx with _C_xxx.

If xxx is data, cgo arranges for C.xxx to refer to the C variable,
with the type translated as described above.  To do this, cgo must
introduce a Go variable that points at the C variable (the linker can

## Changes to the language {#language}...

	for _, w := range walkers {
		for _, name := range w.stdPackages {
			pkg, err := w.import_(name)
			if _, nogo := err.(*build.NoGoError); nogo {
				continue
			}
			if err != nil {
				log.Fatalf("Import(%q): %v", name, err)
			}
			w.export(pkg)
		}

		ctxName := contextName(w.context)
		for _, f := range w.Features() {
			if featureCtx[f] == nil {