| commit | c44ce3df427b8cd50fcbde874ab49535b66cf98c | [log] [tgz] |
|---|---|---|
| author | Jacob Bramley <jacob.bramley@arm.com> | Tue Jun 12 15:39:09 2018 +0100 |
| committer | Jacob Bramley <jacob.bramley@arm.com> | Thu Sep 06 15:41:13 2018 +0100 |
| tree | 08c134093e4794375698c05a340033beccbbe167 | |
| parent | ab70ab91f2ecc24ef5ad4e4cebf6d2021b919166 [diff] |
Check CPU features in the Simulator and Disassembler. This is implemented using a new decoder visitor, CPUFeaturesAuditor. This visitor holds a set of features required by the last-decoded instruction, a set of features seen since construction (or 'ResetSeenFeatures()'), and a set of features that are considered to be available. This visitor can be used by itself, but its main purpose is to implement Simulator and Disassembler support for CPUFeatures: - The Simulator creates and attaches this visitor automatically, much like it does for the disassembly trace, so existing simulation use-cases require no special user interaction. The Simulator checks that each encountered instruction only uses available features. The Simulator also supports dynamic configuration of features, in a manner similar to the trace controls. - The Disassembler does not directly interact with the CPUFeaturesAuditor, but the PrintDisassembler can be configured to annotate each instruction with required features that are missing from GetAvailableFeatures(). The PrintDisassembler is used to implement Simulator trace, so a simulation failure due to missing feature support will be immediately preceeded by a corresponding PrintDisassembler annotation (when trace is enabled). No existing test uses the PrintDisassembler in this way, so this patch also adds 'TRACE_' tests to check that the features are appropriately formatted. Change-Id: I3dc0e22f0a5bd3287ba1870539e018ff4a768a4b
Contents:
VIXL contains three components.
The VIXL git repository can be found on 'https://git.linaro.org'.
Changes from previous versions of VIXL can be found in the Changelog.
This software is covered by the licence described in the LICENCE file.
To build VIXL the following software is required:
A 64-bit host machine is required, implementing an LP64 data model. VIXL has been tested using GCC on AArch64 Debian, GCC and Clang on amd64 Ubuntu systems.
To run the linter and code formatting stages of the tests, the following software is also required:
cpplint.pyRefer to the 'Usage' section for details.
VIXL was developed for JavaScript engines so a number of features from A64 were deemed unnecessary:
The VIXL simulator supports only those instructions that the VIXL assembler can generate. The doc directory contains a list of supported A64 instructions.
The VIXL simulator was developed to run on 64-bit amd64 platforms. Whilst it builds and mostly works for 32-bit x86 platforms, there are a number of floating-point operations which do not work correctly, and a number of tests fail as a result.
VIXL may not build using Clang 3.7, due to a compiler warning. A workaround is to disable conversion of warnings to errors, or to delete the offending return statement reported and rebuild. This problem will be fixed in the next release.
Your project's build system must define VIXL_DEBUG (eg. -DVIXL_DEBUG) when using a VIXL library that has been built with debug enabled.
Some classes defined in VIXL header files contain fields that are only present in debug builds, so if VIXL_DEBUG is defined when the library is built, but not defined for the header files included in your project, you will see runtime failures.
All exclusive-access instructions are supported, but the simulator cannot accurately simulate their behaviour as described in the ARMv8 Architecture Reference Manual.
__sync_synchronize() is used for this purpose.The simulator tries to be strict, and implements the following restrictions that the ARMv8 ARM allows:
Instructions affected by these limitations: stxrb, stxrh, stxr, ldxrb, ldxrh, ldxr, stxp, ldxp, stlxrb, stlxrh, stlxr, ldaxrb, ldaxrh, ldaxr, stlxp, ldaxp, stlrb, stlrh, stlr, ldarb, ldarh, ldar, clrex.
The helper script tools/test.py will build and run every test that is provided with VIXL, in both release and debug mode. It is a useful script for verifying that all of VIXL's dependencies are in place and that VIXL is working as it should.
By default, the tools/test.py script runs a linter to check that the source code conforms with the code style guide, and to detect several common errors that the compiler may not warn about. This is most useful for VIXL developers. The linter has the following dependencies:
git clone.cpplint.py, as provided by Google, must be available (and executable) on the PATH.It is possible to tell tools/test.py to skip the linter stage by passing --nolint. This removes the dependency on cpplint.py and Git. The --nolint option is implied if the VIXL project is a snapshot (with no .git directory).
Additionally, tools/test.py tests code formatting using clang-format-3.8. If you don't have clang-format-3.8, disable the test using the --noclang-format option.
Also note that the tests for the tracing features depend upon external diff and sed tools. If these tools are not available in PATH, these tests will fail.
We have separate guides for introducing VIXL, depending on what architecture you are targeting. A guide for working with AArch32 can be found here, while the AArch64 guide is here. Example source code is provided in the examples directory. You can build examples with either scons aarch32_examples or scons aarch64_examples from the root directory, or use scons --help to get a detailed list of available build targets.