[roll] Roll fuchsia [zircon][utest] Do not check for the bottom 3 bits of DBGWVR The core-address-tagging test fails on bringup.arm64-[thin]lto builders in release mode. This is because an assert fails that checks the bottom 3 bits of the DBGWVR that we assign. The initial reasoning for this was because the bottom bits of DBGWVR are reserved according to the spec. This is slightly incorrect though. First is it's actually the bottom 2 bits that are reserved, not 3. Second, these bottom 2 reserved bits are alsi ignored according to the spec. From `D2.10.4 Watchpoint data address comparisons`: ``` DBGWVR<n>_EL1[1:0] are RES0 and are ignored. ``` Original-Fixed: 103228 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/693834 Original-Revision: 872f5e5cae05c149295733f88654badc78d93467 GitOrigin-RevId: 47e667c041d779340142029155096fadaca6b6be Change-Id: I6de1eb77c3d2167e73cd582dd7a9dcb27c080596
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.