- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for Hodges (0.19 sec)
-
src/cmd/cgo/ast.go
} f.walk(ast2, ctxProg, (*File).validateIdents) f.walk(ast2, ctxProg, (*File).saveExprs) // Accumulate exported functions. // The comments are only on ast1 but we need to // save the function bodies from ast2. // The first walk fills in ExpFunc, and the // second walk changes the entries to // refer to ast2 instead. f.walk(ast1, ctxProg, (*File).saveExport) f.walk(ast2, ctxProg, (*File).saveExport2)
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Jun 07 16:54:27 GMT 2023 - 14.3K bytes - Viewed (0) -
src/cmd/cgo/doc.go
type _Ctype_char int8 type _Ctype_int int32 type _Ctype_void [0]byte The _cgo_gotypes.go file also contains the definitions of the functions. They all have similar bodies that invoke runtime·cgocall to make a switch from the Go runtime world to the system C (GCC-based) world. For example, here is the definition of _Cfunc_puts: //go:cgo_import_static _cgo_be59f0f25121_Cfunc_puts
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) -
doc/asm.html
<code>cmd/internal/obj/x86/a.out.go</code>. </p> <p> The architectures share syntax for common addressing modes such as <code>(R1)</code> (register indirect), <code>4(R1)</code> (register indirect with offset), and <code>$foo(SB)</code> (absolute address). The assembler also supports some (not necessarily all) addressing modes specific to each architecture. The sections below list these. </p> <p>
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) -
doc/go_spec.html
</li> <li> Both type parameters have a known type argument and the type arguments unify per the given matching modes. </li> </ul> <p> A single bound type parameter <code>P</code> and another type <code>T</code> unify per the given matching modes if: </p> <ul> <li> <code>P</code> doesn't have a known type argument.
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu May 02 22:43:51 GMT 2024 - 279.6K bytes - Viewed (0) -
src/cmd/asm/doc.go
Remove prefix from recorded source file paths. -v Print debug output. Input language: The assembler uses mostly the same syntax for all architectures, the main variation having to do with addressing modes. Input is run through a simplified C preprocessor that implements #include, #define, #ifdef/endif, but not #if or ##. For more information, see https://golang.org/doc/asm. */
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Aug 22 20:46:45 GMT 2023 - 1.8K bytes - Viewed (0) -
doc/go_mem.html
would never access <code>*p</code> or <code>*q</code>, but the rewritten program would. And if the call contained synchronizing operations, then the original program could establish happens before edges preceding the accesses to <code>*p</code> and <code>*q</code>, but the rewritten program would not. </p> <p> Not allowing a single read to observe multiple values means
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Mon Mar 04 15:54:42 GMT 2024 - 26.6K bytes - Viewed (0) -
src/cmd/asm/internal/asm/asm.go
// The Loong64 RDTIME family of instructions is a bit special, // in that both its register operands are outputs prog.To = a[0] if a[1].Type != obj.TYPE_REG { p.errorf("invalid addressing modes for 2nd operand to %s instruction, must be register", op) return } prog.RegTo2 = a[1].Reg break } } prog.From = a[0] prog.To = a[1] case 3: switch p.arch.Family {
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Feb 21 14:34:57 GMT 2024 - 25.3K bytes - Viewed (0)