Do not emit double values at their use sites.
Revert part of r14179. From the regression test's comment: Currently, the gap resolver doesn't handle moves from a ConstantOperand to a DoubleRegister, but these kind of moves appeared when HConstant::EmitAtUses was changed to allow special double values (-0, NaN, hole). So we should either enhance the gap resolver or make sure that such moves don't happen. BUG=chrome:234101 Review URL: https://codereview.chromium.org/14429002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@14394 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
This commit is contained in:
parent
c46cbccefd
commit
cd34acdae3
@ -3288,9 +3288,7 @@ class HConstant: public HTemplateInstruction<0> {
|
||||
return has_int32_value_;
|
||||
}
|
||||
|
||||
virtual bool EmitAtUses() {
|
||||
return !representation().IsDouble() || IsSpecialDouble();
|
||||
}
|
||||
virtual bool EmitAtUses() { return !representation().IsDouble(); }
|
||||
virtual void PrintDataTo(StringStream* stream);
|
||||
virtual HType CalculateInferredType();
|
||||
bool IsInteger() { return handle()->IsSmi(); }
|
||||
|
42
test/mjsunit/regress/regress-234101.js
Normal file
42
test/mjsunit/regress/regress-234101.js
Normal file
@ -0,0 +1,42 @@
|
||||
// Copyright 2013 the V8 project authors. All rights reserved.
|
||||
// Redistribution and use in source and binary forms, with or without
|
||||
// modification, are permitted provided that the following conditions are
|
||||
// met:
|
||||
//
|
||||
// * Redistributions of source code must retain the above copyright
|
||||
// notice, this list of conditions and the following disclaimer.
|
||||
// * Redistributions in binary form must reproduce the above
|
||||
// copyright notice, this list of conditions and the following
|
||||
// disclaimer in the documentation and/or other materials provided
|
||||
// with the distribution.
|
||||
// * Neither the name of Google Inc. nor the names of its
|
||||
// contributors may be used to endorse or promote products derived
|
||||
// from this software without specific prior written permission.
|
||||
//
|
||||
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
||||
// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
||||
// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
||||
// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
||||
// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
||||
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
||||
// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
||||
// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
||||
// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
||||
// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
||||
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
|
||||
// Flags: --allow-natives-syntax
|
||||
|
||||
// Currently, the gap resolver doesn't handle moves from a ConstantOperand to a
|
||||
// DoubleRegister, but these kind of moves appeared when HConstant::EmitAtUses
|
||||
// was changed to allow special double values (-0, NaN, hole). So we should
|
||||
// either enhance the gap resolver or make sure that such moves don't happen.
|
||||
|
||||
function foo(x) {
|
||||
return (x ? NaN : 0.2) + 0.1;
|
||||
}
|
||||
|
||||
foo(false);
|
||||
foo(false);
|
||||
%OptimizeFunctionOnNextCall(foo);
|
||||
foo(false);
|
Loading…
Reference in New Issue
Block a user