From fe7f7aa33d085ed3097ab499277c63aafdfd0e5c Mon Sep 17 00:00:00 2001 From: Vladimir Marko Date: Fri, 27 Oct 2023 11:05:27 +0200 Subject: Replace `gUseReadBarrier` with compiler option in compiler. Leave a few `gUseReadBarrier` uses in JNI macro assemblers. We shall deaal with these later. Test: m test-art-host-gtest Test: testrunner.py --host --optimizing Test: run-gtests.sh Test: testrunner.py --target --optimizing Bug: 289805127 Change-Id: I9d2aa245cee4c650129f169a82beda7dc0dd6a35 --- compiler/jit/jit_compiler.cc | 3 +++ 1 file changed, 3 insertions(+) (limited to 'compiler/jit/jit_compiler.cc') diff --git a/compiler/jit/jit_compiler.cc b/compiler/jit/jit_compiler.cc index 86c0f80974..1d9cd571ed 100644 --- a/compiler/jit/jit_compiler.cc +++ b/compiler/jit/jit_compiler.cc @@ -66,6 +66,9 @@ void JitCompiler::ParseCompilerOptions() { // JIT is never PIC, no matter what the runtime compiler options specify. compiler_options_->SetNonPic(); + // Set the appropriate read barrier option. + compiler_options_->emit_read_barrier_ = gUseReadBarrier; + // If the options don't provide whether we generate debuggable code, set // debuggability based on the runtime value. if (!compiler_options_->GetDebuggable()) { -- cgit v1.2.3-59-g8ed1b