tree ad78c4e375c95a96e200baa2786e748505ab928b
parent f12dd5861e0eaf1822c12137fd353b5e79761a6c
author Ulyana Trafimovich <skvadrik@google.com> 1594912178 +0000
committer Ulyana Trafimovich <skvadrik@google.com> 1594983867 +0000

Revert^2 "VIXL simulator for ART (Stage1)"

This reverts commit 3060bb919cd2f37c6a97e87c1581ac5294af72b3.

Reason for revert: relanding original change. The fix is setting
`device_supported: false` for libart(d)-simulator module in the .bp
file (`m checkbuild` attempted to build it for arm32 and failed).
Original commit message:

VIXL simulator for ART (Stage1)

Quick User Guide: test/README.simulator.md

This CL enables running ART run-tests in a simulator on host machine.
Some benefits of using this simulator approach:
- No need to use a target device at all.
  Save developers from solving the device troubles: build, flash, usb,
  adb, etc.
- Speed up development/debug/test cycle.
- Allows easy debugging/testing new instruction features without real
  hardware.
- Allows using a smaller AOSP Android manifest master-art.

The Stage1 CL provides support for running 30% of current run-tests.
The rest unsupported test cases are kept in knownfailures.json.

Future work will be supporting proper stack frame layout between
simulator and quick entrypoints, so that stack walk,
QuickArgumentVisitor, deoptimization, etc can be supported.

This CL adds libart(d)-simulator-container library to the ART APEX. It
has caused the following increase of the APEX size (small, about 0.13%
for release APEX, measured for target aosp_arm64-userdebug):
 Before:
   88992 com.android.art.debug.apex
   51612 com.android.art.release.apex
  112352 com.android.art.testing.apex
 After:
   89124 com.android.art.debug.apex
   51680 com.android.art.release.apex
  112468 com.android.art.testing.apex

Change-Id: I461c80aa9c4ce0673eef1c0254d2c539f2b6a8d5
Test: art/test.py --run-test --optimizing --simulate-arm64
Test: art/test.py --run-test --optimizing --host
Test: m test-art-host-gtest