From 579885a26d761f5ba9550f2a1cd7f0f598c2e1e3 Mon Sep 17 00:00:00 2001 From: Serban Constantinescu Date: Sun, 22 Feb 2015 20:51:33 +0000 Subject: Opt Compiler: ARM64: Enable explicit memory barriers over acquire/release Implement remaining explicit memory barrier code paths and temporarily enable the use of explicit memory barriers for testing. This CL also enables the use of instruction set features in the ARM64 backend. kUseAcquireRelease has been replaced with PreferAcquireRelease(), which for now is statically set to false (prefer explicit memory barriers). Please note that we still prefer acquire-release for the ARM64 Optimizing Compiler, but we would like to exercise the explicit memory barrier code path too. Change-Id: I84e047ecd43b6fbefc5b82cf532e3f5c59076458 Signed-off-by: Serban Constantinescu --- compiler/optimizing/code_generator.cc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'compiler/optimizing/code_generator.cc') diff --git a/compiler/optimizing/code_generator.cc b/compiler/optimizing/code_generator.cc index 2a57fdc929..ba5f7d8fab 100644 --- a/compiler/optimizing/code_generator.cc +++ b/compiler/optimizing/code_generator.cc @@ -386,7 +386,9 @@ CodeGenerator* CodeGenerator::Create(HGraph* graph, compiler_options); } case kArm64: { - return new arm64::CodeGeneratorARM64(graph, compiler_options); + return new arm64::CodeGeneratorARM64(graph, + *isa_features.AsArm64InstructionSetFeatures(), + compiler_options); } case kMips: return nullptr; -- cgit v1.2.3-59-g8ed1b