HomeSort by relevance Sort by last modified time
    Searched refs:execution (Results 1 - 25 of 71) sorted by null

1 2 3

  /external/eclipse-windowbuilder/propertysheet/src/org/eclipse/wb/internal/core/utils/execution/
RunnableEx.java 11 package org.eclipse.wb.internal.core.utils.execution;
RunnableObjectEx.java 11 package org.eclipse.wb.internal.core.utils.execution;
ExecutionUtils.java 11 package org.eclipse.wb.internal.core.utils.execution;
80 * @return <code>true</code> if execution was finished without exception.
94 * @return <code>true</code> if execution was finished without exception.
  /external/oprofile/events/mips/vr5432/
events 6 event:0x2 counters:0,1 um:zero minimum:500 name:LOAD_PREF_CACHE_INSTRUCTIONS : Load, prefetch/CacheOps execution (no sync)
7 event:0x3 counters:0,1 um:zero minimum:500 name:STORES : Store execution
8 event:0x4 counters:0,1 um:zero minimum:500 name:BRANCHES : Branch execution (no jumps or jump registers)
9 event:0x5 counters:0,1 um:zero minimum:500 name:FP_INSTRUCTIONS : (FP instruction execution) / 2 and truncated excluding cp1 loads and stores
  /external/oprofile/events/mips/20K/
events 8 event:0x2 counters:0 um:zero minimum:500 name:FETCH_GROUPS : Fetch groups entering CPU execution pipes
11 event:0x5 counters:0 um:zero minimum:500 name:BRANCHES_MISSPREDICTED : Branches that mispredicted before completing execution
12 event:0x6 counters:0 um:zero minimum:500 name:BRANCHES_COMPLETED : Branches that completed execution
19 event:0xd counters:0 um:zero minimum:500 name:JR_INSNS_COMPLETED : JR instruction that completed execution
21 event:0xf counters:0 um:zero minimum:500 name:INSNS_COMPLETED : Instruction that completed execution (with or without exception)
  /external/eclipse-windowbuilder/propertysheet/src/org/eclipse/wb/internal/core/utils/ui/dialogs/
StringsDialog.java 18 import org.eclipse.wb.internal.core.utils.execution.ExecutionUtils;
19 import org.eclipse.wb.internal.core.utils.execution.RunnableObjectEx;
  /external/llvm/bindings/ocaml/executionengine/
llvm_executionengine.mli 12 This interface provides an ocaml API for LLVM execution engine (JIT/
19 and receive values from the execution engine. It supports only a limited
84 (** An execution engine is either a JIT compiler or an interpreter, capable of
89 (** [create m] creates a new execution engine, taking ownership of the
91 interpreter. Raises [Error msg] if an error occurrs. The execution engine
98 execution engine is not garbage collected and must be destroyed with
105 level [optlevel]. Raises [Error msg] if an error occurrs. The execution
110 (** [dispose ee] releases the memory used by the execution engine and must be
114 (** [add_module m ee] adds the module [m] to the execution engine [ee]. *)
117 (** [remove_module m ee] removes the module [m] from the execution engin
    [all...]
  /external/chromium/net/base/
effective_tld_names_unittest2.cc 28 #error "gperf generated tables don't work with this execution character set. Please report a bug to <bug-gnu-gperf@gnu.org>."
effective_tld_names_unittest1.cc 28 #error "gperf generated tables don't work with this execution character set. Please report a bug to <bug-gnu-gperf@gnu.org>."
  /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/launch/junit/runtime/
AndroidTestReference.java 45 public void run(TestExecution execution) {
RemoteAdtTestRunner.java 38 * Supports Eclipse JUnit execution of Android tests.
48 /** the delay between each test execution when in collecting test info */
74 * <li>The test execution result for each test method. Expects individual notifications of
75 * the test execution start, any failures, and the end of the test execution.</li>
81 * executing the tests, and send it back to JDT JUnit. The second is the actual test execution,
87 * @param execution used to report test progress
90 public void runTests(String[] testClassNames, String testName, TestExecution execution) {
91 // hold onto this execution reference so it can be used to report test progress
92 mExecution = execution;
    [all...]
  /sdk/emulator/tests/
Android.mk 6 # The test-qemud-pipes program is used to check the execution of QEMUD Pipes
  /external/eclipse-windowbuilder/propertysheet/src/org/eclipse/wb/internal/core/model/property/editor/string/
StringPropertyDialog.java 24 import org.eclipse.wb.internal.core.utils.execution.ExecutionUtils;
25 import org.eclipse.wb.internal.core.utils.execution.RunnableEx;
  /external/oprofile/events/mips/25K/
events 14 event:0x8 counters:0,1 um:zero minimum:500 name:INSNS_COMPLETE : Instruction that completed execution (with or without exception)
15 event:0x9 counters:0,1 um:zero minimum:500 name:FETCH_GROUPS_IN_PIPE : Fetch groups entering CPU execution pipes
27 event:0xd counters:0,1 um:zero minimum:500 name:BRANCHES_MISSPREDICTED : Branches that mispredicted before completing execution
28 event:0xe counters:0,1 um:zero minimum:500 name:BRANCHES_COMPLETED : Branches that completed execution
30 event:0x10 counters:0,1 um:zero minimum:500 name:JR_COMPLETED : JR instruction that completed execution
  /development/tools/apkcheck/
Android.mk 21 # the execution script
  /external/eclipse-windowbuilder/propertysheet/src/org/eclipse/wb/internal/core/model/property/editor/
AbstractComboBoxPropertyEditor.java 17 import org.eclipse.wb.internal.core.utils.execution.ExecutionUtils;
18 import org.eclipse.wb.internal.core.utils.execution.RunnableEx;
  /external/mesa3d/docs/
MESA_shader_debug.spec 44 during execution, issue diagnostic function calls that are logged
153 They are used to track the execution of a shader by logging
155 retrieved by the application for inspection after shader execution
  /external/mesa3d/docs/OLD/
MESA_trace.spec 63 Further, IHV's might have builtin support for tracing GL execution
171 The tracing facility is used to record the execution of a GL program
MESA_program_debug.spec 45 2. Query the current program string's execution position.
59 The current execution position (as an offset from the start of the
220 during program execution. GetProgramRegisterfvMESA may only be
  /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/layout/properties/
FlagXmlPropertyDialog.java 40 import org.eclipse.wb.internal.core.utils.execution.ExecutionUtils;
41 import org.eclipse.wb.internal.core.utils.execution.RunnableEx;
  /development/ide/xcode/ports/
skia_mac.cp 21 // argv[0] is set to the execution path of the application, e.g.
  /external/v8/test/mjsunit/
debug-stepin-builtin.js 39 // and than check that execution is paused inside function
debug-stepout-to-builtin.js 39 // and than check that execution is paused inside function
  /external/webkit/PerformanceTests/SunSpider/
sunspider 58 --shark Sample execution time with the Mac OS X "Shark" performance testing tool (implies --runs=1)
  /external/oprofile/events/i386/nehalem/
unit_masks 235 0x04 rs_full This event counts the number of cycles when the number of instructions in the pipeline waiting for execution reaches the limit the processor can handle
238 0x20 fpcw Counts the number of cycles while execution was stalled due to writing the floating-point unit (FPU) control word
240 0x80 other Counts the number of cycles while execution was stalled due to other resource issues
315 0x01 flags Counts the number of cycles during which execution stalled due to several reasons, one of which is a partial flag register stall
316 0x02 registers This event counts the number of cycles instruction execution latency became longer than the defined latency because the instruction used a register that was partially written by previous instruction
319 0x0F any Counts all Register Allocation Table stall cycles due to: Cycles when ROB read port stalls occurred, which did not allow new micro-ops to enter the execution pipe

Completed in 1677 milliseconds

1 2 3