summaryrefslogtreecommitdiff
path: root/compiler/optimizing/graph_visualizer.cc
diff options
context:
space:
mode:
authorHans Boehm <hboehm@google.com>2018-09-05 16:45:42 -0700
committerHans Boehm <hboehm@google.com>2018-09-11 16:55:05 -0700
commitfb8b4e289edd5e838c1ceb4c2fd499e232be845c (patch)
tree33870b1d269e7dbd41705103fa29b5f6f31a324b /compiler/optimizing/graph_visualizer.cc
parent527dee5aab18e7d1dae9cfbe6446e5d2b7e57137 (diff)
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
Diffstat (limited to 'compiler/optimizing/graph_visualizer.cc')
0 files changed, 0 insertions, 0 deletions