[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.
```

Fixed: 103228
Change-Id: I0ca9be74f9d96ba01aea7b4770c0a59ded69d29a
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/693834
Reviewed-by: Roland McGrath <mcgrathr@google.com>
Commit-Queue: Leonard Chan <leonardchan@google.com>
1 file changed
tree: 9eaa4a40185191b0ac28d5e0be1f7d1db19ee587
  1. boards/
  2. build/
  3. bundles/
  4. docs/
  5. examples/
  6. products/
  7. scripts/
  8. sdk/
  9. src/
  10. third_party/
  11. tools/
  12. zircon/
  13. .clang-format
  14. .clang-tidy
  15. .editorconfig
  16. .git-blame-ignore-revs
  17. .gitattributes
  18. .gitignore
  19. .gn
  20. .style.yapf
  21. analysis_options.yaml
  22. AUTHORS
  23. BUILD.gn
  24. CODE_OF_CONDUCT.md
  25. CONTRIBUTING.md
  26. LICENSE
  27. OWNERS
  28. PATENTS
  29. pyrightconfig.json
  30. README.md
  31. rustfmt.toml
README.md

Fuchsia

What is Fuchsia?

Fuchsia is an open source, general purpose operating system supporting modern 64-bit Intel and ARM processors.

We expect everyone interacting with our project to respect our code of conduct.

Read more about Fuchsia's principles.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.