tree 33870b1d269e7dbd41705103fa29b5f6f31a324b
parent 527dee5aab18e7d1dae9cfbe6446e5d2b7e57137
author Hans Boehm <hboehm@google.com> 1536191142 -0700
committer Hans Boehm <hboehm@google.com> 1536710105 -0700

Clean up allocation accounting

Add a "RACING_DCHECK" for counter comparisons that are read with
memory_order_relaxed, and thus might legitimately be inconsistent.
This is a hack, but so long as it's only used for DCHECKs, it seems
better than other available options.

Several counters used inconsistent memory_order specifications.
Generally move those to memory_order_relaxed for informational counters
where the value does not affect code execution in a way that matters
for correctness, and where performance might be an issue.

In cases in which performance is clearly not an issue, just remove
the memory_order specifications, thus no longer erroneously implying
that we've actually thought about ordering.

Improve comments in a few places where I found them confusing.

Bug: 79921586

Test: build and boot AOSP.
Change-Id: I8d0115817a9ff47708ed5e92e8c9caca7e73f899