Fix shouldTranslate() for Optimize translations
commitc40895d92ce5a4abae34dd86552ec6ee4e660b86
authorGuilherme Ottoni <ottoni@fb.com>
Thu, 9 Oct 2014 00:29:10 +0000 (8 17:29 -0700)
committerhhvm-bot <hhvm-bot@fb.com>
Sat, 11 Oct 2014 00:00:24 +0000 (10 17:00 -0700)
treec6548f31089d7ab191c0ac0558dddbdea47b8528
parent4b1db9c87531f3d243c63f00b72238b69435c48a
Fix shouldTranslate() for Optimize translations

Summary: We used to allow Optimize translations regardless of the
Eval.JitAMaxUsage limit, but I recently broke that while refactoring
the code to use shouldTranslate() to also check the
Eval.JitGlobalTranslationLimit limit.  This diff fixes the issue.

Reviewed By: @swtaarrs

Differential Revision: D1604752
hphp/runtime/vm/jit/mc-generator.cpp
hphp/runtime/vm/jit/mc-generator.h