diff options
| author | 2023-11-16 17:44:29 -0800 | |
|---|---|---|
| committer | 2023-11-17 18:36:53 +0000 | |
| commit | de6567b8fc3a08ac70ffbfef0fb4d73009b1d895 (patch) | |
| tree | 9524bd2ce9eafb04cbeb276bf446aafd8669c9d0 /runtime/class_loader_context_test.cc | |
| parent | 5424283b62c436dbb67b665992454a1dc8061953 (diff) | |
Use acquire/release for mark_stack_mode_
The old mixture of relaxed and seq_cst didn't make sense. Letting them
all default to seq_cst would also be fine. On ARM64, this currently
generates the same code as seq_cst, but this saves a few fences on
ARM32 and X86.
Clarify that is_mark_stack_push_disallowed_ is only a debugging tool,
and access it only in debug builds.
Mark some mysterious ThreadFenceForConstructor calls as such for now.
They should be removed unless we can come up with a rationale for
them.
Bug: 120623963
Test: TreeHugger
Change-Id: I86aa4c6bb1fcb1484d050823f8d6a0616418f6d0
Diffstat (limited to 'runtime/class_loader_context_test.cc')
0 files changed, 0 insertions, 0 deletions