Home
last modified time | relevance | path

Searched refs:pipeline (Results 1 – 25 of 40) sorted by relevance

12

/dragonfly/usr.bin/man/
H A Dman.sh306 local IFS pipeline testline
343 pipeline="mandoc -Tps $mandoc_args"
431 e) pipeline="$pipeline | $EQN" ;;
433 p) pipeline="$pipeline | $PIC" ;;
434 r) pipeline="$pipeline | $REFER" ;;
435 t) pipeline="$pipeline | $TBL" ;;
436 v) pipeline="$pipeline | $VGRIND" ;;
441 pipeline="${pipeline#" | "}"
443 pipeline="$TBL"
447 pipeline="$pipeline | $TROFF"
[all …]
/dragonfly/bin/sh/
H A Dnodetypes62 NPIPE npipe # a pipeline
64 backgnd int # set to run pipeline in background
65 cmdlist nodelist # the commands in the pipeline
143 NNOT nnot # ! command (actually pipeline)
H A Dparser.c118 static union node *pipeline(void);
352 n = pipeline(); in andor()
362 n = makebinary(t, n, pipeline()); in andor()
369 pipeline(void) in pipeline() function
396 lp->n = pipeline(); in pipeline()
H A DTOUR207 if the command is not found. (When a pipeline is set up,
208 find_command is called for all the commands in the pipeline be-
/dragonfly/contrib/gcc-4.7/gcc/config/i386/
H A Dk6.md116 ;; ??? Guessed latencies based on the old pipeline description.
193 ;; The load and units have two pipeline stages. The load latency is
206 ;; ??? From the old pipeline description. Egad!
262 ;; ??? Guessed latencies from the old pipeline description.
H A Dgeode.md34 ;; issue describes the issue pipeline.
39 ;; There is also memory management unit and execution pipeline for
H A Dpentium.md93 ;; instructions. We model only first cycle of FP pipeline, as it is
207 ;; in FP pipeline allowing other instructions to be executed.
H A Dcore2.md26 ;; The major difference from the P6 pipeline is one extra decoder, and
H A Dppro.md33 ;; The P6 pipeline has three major components:
H A Dbdver1.md96 ;; The FP operations start to execute at stage 12 in the pipeline, while
/dragonfly/contrib/gcc-8.0/gcc/config/i386/
H A Dk6.md115 ;; ??? Guessed latencies based on the old pipeline description.
192 ;; The load and units have two pipeline stages. The load latency is
205 ;; ??? From the old pipeline description. Egad!
261 ;; ??? Guessed latencies from the old pipeline description.
H A Dgeode.md33 ;; issue describes the issue pipeline.
38 ;; There is also memory management unit and execution pipeline for
H A Dpentium.md93 ;; instructions. We model only first cycle of FP pipeline, as it is
207 ;; in FP pipeline allowing other instructions to be executed.
H A Dhaswell.md21 ;; The major difference from the CORE2 pipeline is that HASWELL has
508 ;; Use skylake pipeline.
H A Dcore2.md26 ;; The major difference from the P6 pipeline is one extra decoder, and
H A Dppro.md33 ;; The P6 pipeline has three major components:
H A Dbdver1.md100 ;; The FP operations start to execute at stage 12 in the pipeline, while
/dragonfly/contrib/binutils-2.27/gas/doc/
H A Dc-tilepro.texi65 pipeline than the next one, etc. This fact, combined with the
67 allows precise control over which pipeline executes each instruction.
70 assembler will automatically try to find a valid pipeline
78 instructions (not @code{fnop}) to fill the remaining pipeline slots in
H A Dc-tilegx.texi81 pipeline than the next one, etc. This fact, combined with the
83 allows precise control over which pipeline executes each instruction.
86 assembler will automatically try to find a valid pipeline
94 instructions (not @code{fnop}) to fill the remaining pipeline slots in
H A Dc-arc.texi449 a short cut in the pipeline. The valid values are:
452 The register has a short cut in the pipeline;
455 The register does not have a short cut in the pipeline.
463 register 57, and can short cut the pipeline.
H A Dc-m32r.texi342 @item Instructions share the same execution pipeline
344 instruction whoes components both use the same execution pipeline.
/dragonfly/sys/kern/
H A Dkern_ktr.c162 KTR_INFO(KTR_TESTLOG, testlog, pipeline, 18, "pipeline");
435 logtest_noargs(pipeline); in ktr_pipeline_remote()
/dragonfly/contrib/gcc-4.7/gcc/doc/
H A Dmd.texi8104 @node Processor pipeline description
8105 @subsection Specifying processor pipeline description
8106 @cindex processor pipeline description
8112 @cindex pipeline hazard recognizer
8113 @cindex automaton based pipeline description
8150 processor parallelism (or @dfn{pipeline description}). GCC
8170 @cindex automaton based pipeline description
8177 @cindex pipeline hazard recognizer
8280 pipeline hazard recognizer work because it would slow down the
8579 are issued into the second pipeline. Integer division and
[all …]
/dragonfly/contrib/gcc-4.7/gcc/
H A Dparams.def585 "max-pipeline-region-blocks",
590 "max-pipeline-region-insns",
/dragonfly/contrib/gcc-8.0/gcc/
H A Dparams.def628 "max-pipeline-region-blocks",
633 "max-pipeline-region-insns",

12