Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(316)

Side by Side Diff: test/mjsunit/regress/regress-2339.js

Issue 10963032: Avoid wrong imul deopt on ia32 and x64 (fixes v8 bug 2339). (Closed) Base URL: https://v8.googlecode.com/svn/branches/bleeding_edge
Patch Set: Addressed review comments. Created 8 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 // Copyright 2012 the V8 project authors. All rights reserved. 1 // Copyright 2012 the V8 project authors. All rights reserved.
2 // Redistribution and use in source and binary forms, with or without 2 // Redistribution and use in source and binary forms, with or without
3 // modification, are permitted provided that the following conditions are 3 // modification, are permitted provided that the following conditions are
4 // met: 4 // met:
5 // 5 //
6 // * Redistributions of source code must retain the above copyright 6 // * Redistributions of source code must retain the above copyright
7 // notice, this list of conditions and the following disclaimer. 7 // notice, this list of conditions and the following disclaimer.
8 // * Redistributions in binary form must reproduce the above 8 // * Redistributions in binary form must reproduce the above
9 // copyright notice, this list of conditions and the following 9 // copyright notice, this list of conditions and the following
10 // disclaimer in the documentation and/or other materials provided 10 // disclaimer in the documentation and/or other materials provided
(...skipping 13 matching lines...) Expand all
24 // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 24 // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
25 // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 25 // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
26 // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 26 // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
27 27
28 // Flags: --allow-natives-syntax --expose-gc 28 // Flags: --allow-natives-syntax --expose-gc
29 29
30 /** 30 /**
31 * The possible optimization states of a function. Must be in sync with the 31 * The possible optimization states of a function. Must be in sync with the
32 * return values of Runtime_GetOptimizationStatus() in runtime.cc! 32 * return values of Runtime_GetOptimizationStatus() in runtime.cc!
33 */ 33 */
34
34 var OptimizationState = { 35 var OptimizationState = {
35 YES: 1, 36 YES: 1,
36 NO: 2, 37 NO: 2,
37 ALWAYS: 3, 38 ALWAYS: 3,
38 NEVER: 4 39 NEVER: 4
39 }; 40 };
40 41
41 function mul (a, b) { 42 function simple() {
42 return a * b; 43 return simple_two_args(0, undefined);
43 } 44 }
44 45
45 mul(-1, -1); 46 function simple_two_args(always_zero, always_undefined) {
46 mul(0x80000001|0, -1); 47 var always_five = always_undefined || 5;
47 mul(0x80000001|0, -1); 48 return always_zero * always_five * .5;
48 %OptimizeFunctionOnNextCall(mul); 49 }
49 mul(0, -1);
50 %OptimizeFunctionOnNextCall(mul);
51 mul(0, -1);
52 50
53 var raw_optimized = %GetOptimizationStatus(mul); 51 for (var i = 0; i < 10000; i++) {
Jakob Kummerow 2012/09/26 09:26:41 can we use %OptimizeFunctionOnNextCall here too? -
52 simple();
53 }
54 var raw_optimized = %GetOptimizationStatus(simple);
54 assertFalse(raw_optimized == OptimizationState.NO); 55 assertFalse(raw_optimized == OptimizationState.NO);
55 gc(); 56 gc();
56 57
OLDNEW
« test/mjsunit/regress/regress-1117.js ('K') | « test/mjsunit/regress/regress-1117.js ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698