HomeSort by relevance Sort by last modified time
    Searched full:instrumented (Results 76 - 100 of 375) sorted by null

1 2 34 5 6 7 8 91011>>

  /external/llvm/test/Instrumentation/InstrProfiling/
PR23499.ll 1 ;; Check that PGO instrumented variables associated with linkonce odr
  /external/robolectric/v1/src/test/java/com/xtremelabs/robolectric/
RobolectricTestRunnerTest.java 68 // Compare exception name because it was loaded in the instrumented classloader
  /external/slf4j/slf4j-ext/src/main/java/org/slf4j/agent/
AgentOptions.java 42 * before the agent cannot be instrumented.
  /external/valgrind/coregrind/
pub_core_gdbserver.h 138 if these are not yet instrumented for gdbserver.
144 instrumented by the tool instrument function i.e. :
150 where sb_out is the block instrumented by the tool.
157 (IRSB* sb_in, /* block to be instrumented */
  /frameworks/base/docs/html/training/testing/integration-testing/
content-provider-testing.jd 81 <a href="{@docRoot}training/testing/start/index.html#run-instrumented-tests">
123 You run integration tests for content providers the same way as instrumented unit tests. To run the
125 href="{@docRoot}training/testing/unit-testing/instrumented-unit-tests.html#run">
126 Run Instrumented Unit Tests</a>.
  /external/clang/docs/
DataFlowSanitizer.rst 46 where a particular library or function cannot be instrumented (e.g. because
49 be instrumented.
ThreadSanitizer.rst 89 Some code should not be instrumented by ThreadSanitizer. One may use the
102 `no_sanitize_thread` attribute, blacklisted functions are not instrumented at
DataFlowSanitizerDesign.rst 168 which conform to the native ABI, each of which is callable from an instrumented
170 function with a reference to a function which uses the instrumented ABI.
213 for a function with the native ABI to be called with the instrumented ABI,
216 "dfs$" to the name of each instrumented-ABI function.
219 across the instrumented-native barrier cannot be used on the other side.
  /external/compiler-rt/lib/asan/
asan_internal.h 26 " instrumented by AddressSanitizer"
57 // functions from the instrumented user code in a profile.
  /external/jacoco/org.jacoco.ant/src/org/jacoco/ant/
AbstractCoverageTask.java 119 * instrumented.
122 * <code>true</code> if bootstrap classes should be instrumented
  /external/jacoco/org.jacoco.core/src/org/jacoco/core/runtime/
LoggerRuntime.java 28 * The implementation uses a dedicated log channel. Instrumented classes call
184 // that might get instrumented during shutdown (e.g. loaded by other
  /external/jacoco/org.jacoco.doc/docroot/doc/
maven.html 122 <li><a href="restore-instrumented-classes-mojo.html">restore-instrumented-classes</a></li>
classids.html 122 tests. This way classes get instrumented by JaCoCo before any runtime
124 generated with the <i>original</i> classes, not with instrumented ones.</li>
139 methods of a class. As a result every instrumented class produces a list of
  /external/llvm/include/llvm/ProfileData/
InstrProf.h 1 //=-- InstrProf.h - Instrumented profiling format support ---------*- C++ -*-=//
10 // Instrumentation-based profiling data is generated by instrumented
46 /// Return the name of data section containing names of instrumented
72 /// Return the name prefix of variables containing instrumented function names.
86 /// for each instrumented source module. Such variables are allocated
102 /// data for one instrumented function.
154 /// and \c Linkage is the linkage of the instrumented function.
337 /// Return the number of instrumented sites for ValueKind.
  /external/robolectric/v1/src/main/java/com/xtremelabs/robolectric/
RobolectricTestRunner.java 59 /** Instrument detector. We use it to check whether the current instance is instrumented. */
71 // fields in the RobolectricTestRunner in the instrumented ClassLoader
237 * loader. This instrumented instance of the test runner, along with the instrumented instance of the actual test,
238 * provides access to Robolectric's features and the un-instrumented instance of the test runner delegates most of
292 * Only used when creating the delegate instance within the instrumented ClassLoader.
624 * Detects whether current instance is already instrumented.
637 * @return true if current instance is already instrumented
  /external/valgrind/docs/internals/
arm_thumb_notes_gdbserver.txt 38 of the instruction being instrumented, the thumb bit must be accessible
45 instruction must be discarded to have the SB re-instrumented for gdbserver.
  /sdk/files/ant/
build.xml 372 <record-build-key key="build.last.is.instrumented" value="${build.is.instrumented}" />
490 <property name="build.last.is.instrumented" value="" />
512 special case for instrumented: if the previous build was
513 instrumented but not this one, clear out the compiled code -->
517 <istrue value="${build.last.is.instrumented}" />
518 <isfalse value="${build.is.instrumented}" />
522 <echo level="info">Switching from instrumented to non-instrumented build: Deleting previous compilation output...</echo>
587 <istrue value="${build.is.instrumented}" />
    [all...]
  /external/valgrind/coregrind/m_gdbserver/
README_DEVELOPERS 57 each instruction is instrumented with an additional call to a dirty
86 to be discarded and then re-instrumented so as to insert calls to a
88 instrumented for gdbserver, all the "jump targets" of this block are
90 blocks will themselves automatically be re-instrumented for gdbserver
92 The valgrind gdbserver remembers which blocks have been instrumented
97 are kept instrumented for gdbserver.
120 instrumented all the instructions of the block for gdbserver even
343 when called from a block not yet instrumented : instead
347 We could detect if the current block is instrumented by a trick
352 from a block which is instrumented. *
    [all...]
  /external/compiler-rt/
CMakeLists.txt 181 # We support running instrumented tests when we're not cross compiling
186 option(COMPILER_RT_CAN_EXECUTE_TESTS "Can we execute instrumented tests" ON)
188 option(COMPILER_RT_CAN_EXECUTE_TESTS "Can we execute instrumented tests" OFF)
  /external/emma/core/java12/com/vladium/emma/report/
AbstractReportGenerator.java 79 m_log.warning ("not all instrumented classes were compiled with source file");
108 m_log.warning ("not all instrumented classes were compiled with line number");
116 m_log.warning ("not all instrumented classes were compiled with line number");
  /cts/build/
device_info_package.mk 16 # Builds a package which can be instrumented to retrieve information about the device under test.
  /cts/tests/sample/src/android/sample/cts/
SampleDeviceReportLogTest.java 54 * Constructor which passes the class of the activity to be instrumented.
SampleDeviceResultTest.java 54 * Constructor which passes the class of the activity to be instrumented.
  /docs/source.android.com/src/devices/tech/debug/
asan.jd 57 <p>As a first step to building an ASan-instrumented binary, make sure that your
201 the dynamic library search path. This way ASan-instrumented
231 <code>/system/lib</code> (the first make invocation), ASan-instrumented in
233 second build overwrite the ones from the first build. ASan-instrumented
  /external/clang/test/Profile/
objc-general.m 10 // Use this to build an instrumented version to regenerate the input file.

Completed in 1834 milliseconds

1 2 34 5 6 7 8 91011>>