- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Lively (0.14 sec)
-
src/cmd/cgo/doc.go
GOEXPERIMENT=cgocheck2 at build time. It is possible to defeat this enforcement by using the unsafe package, and of course there is nothing stopping the C code from doing anything it likes. However, programs that break these rules are likely to fail in unexpected and unpredictable ways. The runtime/cgo.Handle type can be used to safely pass Go values between Go and C. See the runtime/cgo package documentation for details.
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Sun Mar 31 09:02:45 GMT 2024 - 42.1K bytes - Viewed (0) -
src/cmd/asm/internal/arch/arch.go
} } func archRISCV64(shared bool) *Arch { register := make(map[string]int16) // Standard register names. for i := riscv.REG_X0; i <= riscv.REG_X31; i++ { // Disallow X3 in shared mode, as this will likely be used as the // GP register, which could result in problems in non-Go code, // including signal handlers. if shared && i == riscv.REG_GP { continue } if i == riscv.REG_TP || i == riscv.REG_G {
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Mar 21 06:51:28 GMT 2023 - 21.3K bytes - Viewed (0) -
doc/asm.html
If you need to use a missing instruction, there are two ways to proceed. One is to update the assembler to support that instruction, which is straightforward but only worthwhile if it's likely the instruction will be used again. Instead, for simple one-off cases, it's possible to use the <code>BYTE</code> and <code>WORD</code> directives
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Tue Nov 28 19:15:27 GMT 2023 - 36.3K bytes - Viewed (0)