Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for instrument2 (0.3 sec)

  1. src/debug/elf/elf.go

    	EM_TI_C6000      Machine = 140 /* The Texas Instruments TMS320C6000 DSP family */
    	EM_TI_C2000      Machine = 141 /* The Texas Instruments TMS320C2000 DSP family */
    	EM_TI_C5500      Machine = 142 /* The Texas Instruments TMS320C55x DSP family */
    	EM_TI_ARP32      Machine = 143 /* Texas Instruments Application Specific RISC Processor, 32bit fetch */
    	EM_TI_PRU        Machine = 144 /* Texas Instruments Programmable Realtime Unit */
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Tue Apr 16 00:01:16 UTC 2024
    - 134.6K bytes
    - Viewed (0)
  2. src/cmd/go/internal/load/pkg.go

    		// If -coverpkg has been specified, then we instrument only
    		// the specific packages selected by the user-specified pattern(s).
    		match = make([]func(*Package) bool, len(cfg.BuildCoverPkg))
    		for i := range cfg.BuildCoverPkg {
    			match[i] = MatchPackage(cfg.BuildCoverPkg[i], base.Cwd())
    		}
    	} else {
    		// Without -coverpkg, instrument only packages in the main module
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Tue May 28 17:00:51 UTC 2024
    - 120K bytes
    - Viewed (0)
  3. src/compress/bzip2/testdata/Isaac.Newton-Opticks.txt.bz2

    comparing it with a pretty good Perspective of four Feet in length, made with a concave Eye-glass, I could read at a greater distance with my own Instrument than with the Glass. Yet Objects appeared much darker in it than in the Glass, and that partly because more Light was lost by Reflexion in the Metal, than by Refraction in the Glass, and partly because my Instrument was overcharged. Had it magnified but 30 or 25 times, it would have made the Object appear more brisk and pleasant. Two of these I made about...
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Mon Sep 24 18:26:02 UTC 2018
    - 129.4K bytes
    - Viewed (0)
  4. src/cmd/go/internal/work/exec.go

    	// The .go file will use import "C" and is to be processed by cgo.
    	// For -cover test or build runs, this needs to happen after the cover
    	// tool is run; we don't want to instrument swig-generated Go files,
    	// see issue #64661.
    	if p.UsesSwig() {
    		outGo, outC, outCXX, err := b.swig(a, objdir, pcCFLAGS)
    		if err != nil {
    			return err
    		}
    		cgofiles = append(cgofiles, outGo...)
    Registered: Wed Jun 12 16:32:35 UTC 2024
    - Last Modified: Mon Jun 10 14:46:37 UTC 2024
    - 105.6K bytes
    - Viewed (0)
Back to top