- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 11 for Messages (0.2 sec)
-
src/cmd/cgo/doc.go
Cgo takes a different approach. It determines the meaning of C identifiers not by parsing C code but by feeding carefully constructed programs into the system C compiler and interpreting the generated error messages, debug information, and object files. In practice, parsing these is significantly less work and more robust than parsing C source. Cgo first invokes gcc -E -dM on the preamble, in order to find out
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/asm/parse.go
func (p *Parser) line(scratch [][]lex.Token) (word, cond string, operands [][]lex.Token, ok bool) { next: // Skip newlines. var tok lex.ScanToken for { tok = p.nextToken() // We save the line number here so error messages from this instruction // are labeled with this line. Otherwise we complain after we've absorbed // the terminating newline and the line numbers are off by one in errors. p.lineNum = p.lex.Line() switch tok {
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Feb 21 14:34:57 GMT 2024 - 36.9K bytes - Viewed (0) -
src/cmd/cgo/internal/swig/swig_test.go
} var ( swigOnce sync.Once haveSwig bool ) func mustHaveSwig(t *testing.T) { swigOnce.Do(func() { mustHaveSwigOnce(t) haveSwig = true }) // The first call will skip t with a nice message. On later calls, we just skip. if !haveSwig { t.Skip("swig not found") } } func mustHaveSwigOnce(t *testing.T) { swig, err := exec.LookPath("swig") if err != nil { t.Skipf("swig not in PATH: %s", err)
Go - Registered: Tue Apr 23 11:13:09 GMT 2024 - Last Modified: Fri May 12 12:00:07 GMT 2023 - 3.7K bytes - Viewed (0) -
src/arena/arena.go
limits the impact of these use-after-free bugs by preventing reuse of freed memory regions until the garbage collector is able to determine that it is safe. Typically, a use-after-free bug will result in a fault and a helpful error message, but this package reserves the right to not force a fault on freed memory. That means a valid implementation of this package is to just allocate all memory the way the runtime normally would, and in fact, it
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Oct 12 20:23:36 GMT 2022 - 4.3K bytes - Viewed (0) -
src/cmd/cgo/gcc.go
return needType } // Coerce gcc into telling us whether each name is a type, a value, or undeclared. // For names, find out whether they are integer constants. // We used to look at specific warning or error messages here, but that tied the // behavior too closely to specific versions of the compilers. // Instead, arrange that we can infer what we need from only the presence or absence // of an error on a specific line. //
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Nov 02 16:43:23 GMT 2023 - 97K bytes - Viewed (0) -
src/cmd/asm/internal/asm/endtoend_test.go
for _, f := range strings.Split(s, " or ") { if f == "" || len(f)%2 != 0 || strings.TrimLeft(f, "0123456789abcdef") != "" { return false } } return true } // It would be nice if the error messages always began with // the standard file:line: prefix, // but that's not where we are today. // It might be at the beginning but it might be in the middle of the printed instruction.
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Thu Dec 07 18:42:59 GMT 2023 - 11.6K bytes - Viewed (0) -
src/cmd/asm/internal/asm/testdata/amd64error.s
// VEX-encoded VSIB can't use High-16 registers as index (unlike EVEX). // TODO(quasilyte): improve error message (#21860). VPGATHERQQ X2, (BP)(X20*2), X3 // ERROR "invalid instruction" VPGATHERQQ Y2, (BP)(Y20*2), Y3 // ERROR "invalid instruction" // YzrMulti4 expects exactly 4 registers referenced by REG_LIST. // TODO(quasilyte): improve error message (#21860). V4FMADDPS (AX), [Z0-Z4], K1, Z7 // ERROR "invalid instruction"
Others - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Jun 14 00:03:57 GMT 2023 - 8.9K bytes - Viewed (0) -
doc/go_spec.html
<h3 id="Type_unification_rules">Type unification rules</h3> <p> The type unification rules describe if and how two types unify. The precise details are relevant for Go implementations, affect the specifics of error messages (such as whether a compiler reports a type inference or other error), and may explain why type inference fails in unusual code situations. But by and large these rules can be ignored when writing Go code:
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/internal/flags/flags.go
// Copyright 2015 The Go Authors. All rights reserved. // Use of this source code is governed by a BSD-style // license that can be found in the LICENSE file. // Package flags implements top-level flags and the usage message for the assembler. package flags import ( "cmd/internal/obj" "cmd/internal/objabi" "flag" "fmt" "os" "path/filepath" "strings" ) var (
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Aug 22 19:18:23 GMT 2023 - 2.8K bytes - Viewed (0) -
api/go1.1.txt
pkg syscall (windows-386), const FORMAT_MESSAGE_ALLOCATE_BUFFER = 256 pkg syscall (windows-386), const FORMAT_MESSAGE_ARGUMENT_ARRAY = 8192 pkg syscall (windows-386), const FORMAT_MESSAGE_FROM_HMODULE = 2048 pkg syscall (windows-386), const FORMAT_MESSAGE_FROM_STRING = 1024 pkg syscall (windows-386), const FORMAT_MESSAGE_FROM_SYSTEM = 4096 pkg syscall (windows-386), const FORMAT_MESSAGE_IGNORE_INSERTS = 512
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu Mar 31 20:37:15 GMT 2022 - 2.6M bytes - Viewed (0)