Put branch profiling under a flag.

Until we evaluate its usefulness and reduce its overhead.

Bug: 306638020

Test: test.py
Change-Id: Ibb01c70a7ea19b03802dcc1b0792d3d2ff4f4d67

1 files changed, 1 insertions, 6 deletions

diff --git a/compiler/optimizing/nodes.h b/compiler/optimizing/nodes.h
index 4db72a68e3..6ec83beabd 100644
--- a/compiler/optimizing/nodes.h
+++ b/compiler/optimizing/nodes.h
@@ -2663,12 +2663,7 @@ class HInstruction : public ArenaObject<kArenaAllocInstruction> {
   void RemoveEnvironmentUsers();
 
   bool IsEmittedAtUseSite() const { return GetPackedFlag<kFlagEmittedAtUseSite>(); }
-  void MarkEmittedAtUseSite() {
-    // When compiling baseline, in order to do branch profiling, we don't want to
-    // emit conditions at use site.
-    DCHECK(!IsCondition() || !GetBlock()->GetGraph()->IsCompilingBaseline());
-    SetPackedFlag<kFlagEmittedAtUseSite>(true);
-  }
+  void MarkEmittedAtUseSite() { SetPackedFlag<kFlagEmittedAtUseSite>(true); }
 
  protected:
   // If set, the machine code for this instruction is assumed to be generated by