Tests that carefully checks opt/deopt status shouldn't --always-opt.

If we optimize a function before gathering feedback it may be
peppered with soft deoptimizations. So it can't help but deoptimize.
A judicious reading of the code isn't enough to determine what the
optimization state should be in the face of such chaotic gyrations.

BUG=
R=verwaest@chromium.org

Review URL: https://codereview.chromium.org/1069363003

Cr-Commit-Position: refs/heads/master@{#27671}

test/mjsunit/double-intrinsics.js

@@ -3,6 +3,7 @@
 // found in the LICENSE file.
 
 // Flags: --allow-natives-syntax
+// Flags: --noalways-opt
 
 function assertDoubleBits(hi, lo, x) {
   hi = hi | 0;

test/mjsunit/es6/block-let-crankshaft.js

@@ -26,6 +26,7 @@
 // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 // Flags: --allow-natives-syntax
+// Flags: --noalways-opt
 
 "use strict";