-
Notifications
You must be signed in to change notification settings - Fork 46
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Provide an email contact address in the README for bug reports. Change-Id: Iad9e8c2f135758da12597ab18fc8ea8d72006174
- Loading branch information
Showing
1 changed file
with
10 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,6 +7,7 @@ Contents: | |
* Licence | ||
* Requirements | ||
* Known limitations | ||
* Bug reports | ||
* Usage | ||
|
||
|
||
|
@@ -63,8 +64,8 @@ Note that in Ubuntu 18.04, clang-tidy-4.0 will only work if the clang-4.0 | |
package is also installed. | ||
|
||
|
||
Known Limitations for AArch64 code generation | ||
============================================= | ||
Known Limitations | ||
================= | ||
|
||
VIXL was developed for JavaScript engines so a number of features from A64 were | ||
deemed unnecessary: | ||
|
@@ -83,11 +84,6 @@ 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. | ||
|
||
Debug Builds | ||
------------ | ||
|
||
|
@@ -162,6 +158,13 @@ instructions precisely, because, subject to the limitations described above, it | |
offers an additional layer of protection against logic bugs in instruction | ||
selection. | ||
|
||
Bug reports | ||
=========== | ||
|
||
Bug reports may be sent to [email protected]. Please provide any steps required to | ||
recreate a bug, along with build environment and host system information. | ||
|
||
|
||
Usage | ||
===== | ||
|
||
|