- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Shing (0.21 sec)
-
doc/asm.html
what is explained in that document, and describes the peculiarities that apply when writing assembly code to interact with Go. </p> <p> The most important thing to know about Go's assembler is that it is not a direct representation of the underlying machine. Some of the details map precisely to the machine, but some do not. This is because the compiler suite (see
HTML - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Nov 28 19:15:27 GMT 2023 - 36.3K bytes - Viewed (0) -
src/cmd/cgo/doc.go
package, such as C.puts. It collects all such identifiers. The next step is to determine each kind of name. In C.xxx the xxx might refer to a type, a function, a constant, or a global variable. Cgo must decide which. The obvious thing for cgo to do is to process the preamble, expanding #includes and processing the corresponding C code. That would require a full C parser and type checker that was also aware of any extensions
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/cgo/gcc.go
origX := *px *px = ast.NewIdent(fmt.Sprintf("_cgoBase%d", i)) fmt.Fprintf(sb, "_cgo%d := %s; ", i, gofmtPos(arg, arg.Pos())) *px = origX // Use "0 == 0" to do the right thing in the unlikely event // that "true" is shadowed. fmt.Fprintf(sbCheck, "_cgoCheckPointer(_cgoBase%d, 0 == 0); ", i) return true } // checkSlice checks whether arg has the form x[i:j], possibly inside
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Nov 02 16:43:23 GMT 2023 - 97K bytes - Viewed (0)