Home
last modified time | relevance | path

Searched refs:architecture (Results 1 – 13 of 13) sorted by relevance

/art/tools/dexfuzz/src/dexfuzz/executors/
DExecutor.java39 protected Architecture architecture; field in Executor
44 protected Executor(String name, int timeout, BaseListener listener, Architecture architecture, in Executor() argument
56 this.architecture = architecture; in Executor()
104 commandBuilder.append("--instruction-set=").append(architecture.asString()); in verifyOnHost()
164 device.cleanCodeCache(architecture, testLocation, programName); in prepareProgramForExecution()
212 return architecture; in getArchitecture()
DDevice.java259 private String getCacheLocation(Architecture architecture) { in getCacheLocation() argument
262 cacheLocation = androidData + "/dalvik-cache/" + architecture.asString() + "/"; in getCacheLocation()
264 cacheLocation = "/data/dalvik-cache/" + architecture.asString() + "/"; in getCacheLocation()
274 public void cleanCodeCache(Architecture architecture, String testLocation, String programName) { in cleanCodeCache() argument
275 String command = getExecutionPrefixWithAdb("shell") + "rm -f " + getCacheLocation(architecture) in cleanCodeCache()
/art/libnativebridge/
DREADME.md8 is useful to bootstrap devices with an architecture that is not supported by the
10 of apps that can be run on that particular architecture).
/art/build/
DREADME.md45 `<arch>` is the device architecture - use `hmm` to see the options.
46 Regardless of the device architecture, the build also includes the usual
/art/tools/checker/
DREADME72 A group of check lines can be made architecture-specific by inserting '-<arch>'
82 'CHECK-START' keyword. Any listed architecture will match in that case,
98 architecture features enabled at compile time. For that purpose, you can call the custom made
/art/test/
DREADME.chroot.md58 2. Select a lunch target corresponding to the architecture you want to
90 2. Select a lunch target corresponding to the architecture you want to
DAndroid.bp218 // Support multilib variants (using different suffix per sub-architecture),
361 // Support multilib variants (using different suffix per sub-architecture), which is needed on
1335 // Support multilib variants (using different suffix per sub-architecture), which is needed on
/art/runtime/arch/arm/
Dinstruction_set_features_arm.cc300 info.architecture == 8)); in FromCpuFeatures()
/art/runtime/interpreter/mterp/
DREADME.txt4 All the architecture-specific template files are concatenated to create
/art/adbconnection/
Dadbconnection.cc628 {.type = AdbConnectionClientInfoType::architecture, in SetupAdbConnection()
630 .data.architecture.name = isa, in SetupAdbConnection()
631 .data.architecture.size = strlen(isa)}, in SetupAdbConnection()
/art/libnativeloader/
DREADME.md32 with the [VNDK-SP](https://source.android.com/devices/architecture/vndk#sp-hal)
/art/compiler/
DAndroid.bp18 // architecture into its own category. Currently we just include all of the 32bit variant in the
520 // This test is testing architecture-independent functionality,
/art/tools/signal_dumper/
Dsignal_dumper.cc383 #error Unsupported architecture in DumpABI()