Home
last modified time | relevance | path

Searched refs:variables (Results 1 – 7 of 7) sorted by relevance

/cts/common/device-side/device-info/src/com/android/compatibility/common/deviceinfo/
DGraphicsDeviceInfo.java77 Set<String> variables = stubActivity.getImplementationVariableNames(); in collectDeviceInfo() local
78 for (String name : variables) { in collectDeviceInfo()
DGlesStubActivity.java456 private void collectImplementationVariables(ImplementationVariable[] variables) { in collectImplementationVariables() argument
457 for (int i = 0; i < variables.length; i++) { in collectImplementationVariables()
458 String name = variables[i].getName(); in collectImplementationVariables()
459 Object value = variables[i].getValue(); in collectImplementationVariables()
460 boolean dynamicArray = variables[i] instanceof DynamicIntVectorValue; in collectImplementationVariables()
/cts/tests/jdwp/runner/host-side/resources/expectations/
Dexternal_oj_libjdwp_art_failures.txt14 …description: "This test is incorrect since it blindly requests local variables without checking th…
/cts/hostsidetests/sustainedperf/dhrystone/
DRationale95 the variables that are computed are not used somehow, there is the
96 danger that the compiler considers them as "dead variables" and
98 version 2 all variables of "main" are printed at the end of the
131 loop and that are not just renamings of variables. All remarks refer to
153 loop in "main ", the role of some variables has been exchanged, to
256 variables, register allocation etc. occuring in other compilation
DDrystone-2.1.sh1251 X /* i.e. no register variables */
/cts/tests/tests/renderscript/src/android/renderscript/cts/
Dsingle_source_alloc.rscript71 // tested. SETELEMENTAT, STORE_TO_ALLOC capture the following variables from
/cts/apps/CameraITS/build/scripts/
Dgpylint_rcfile75 # note). You have access to the variables errors warning, statement which