{"push_id":788310553,"size":5,"distinct_size":0,"ref":"refs/heads/roll","head":"6b3c070db6e1e2e631f265410f540ec1a6df92ee","before":"f852f56cb285e1e54be09f5cc9e6401520b85147","commits":[{"sha":"0cfa52d055586fe632564812e0a05b2a65612b90","author":{"email":"bcb9ee19c6091ae3933290f91179ddd82d15e2f0@intel.com","name":"chunyang.dai"},"message":"X87: [runtime] Replace many buggy uses of %_CallFunction with %_Call.\n\nport db2ba190dba6983b94eae36e111b0feebb97587e (r30634).\n\noriginal commit message:\n\n    The semantics of the %_CallFunction intrinsic seem to be very unclear,\n    which resulted in a lot of bugs. Especially the combination with\n    %IsSloppyModeFunction is always a bug, because the receiver would be\n    wrapped in the wrong context. So the %IsSloppyModeFunction helper is\n    gone now, and many of the buggy uses of %_CallFunction are also\n    eliminated.\n\n    If you ever need to call something with a different receiver, then\n    %_Call is your friend now. It does what you want and implements the\n    call sequence fully (and correct).\n\nReview URL: https://codereview.chromium.org/1336443002\n\nCr-Commit-Position: refs/heads/master@{#30667}","distinct":false,"url":"https://api.github.com/repos/v8/v8-git-mirror/commits/0cfa52d055586fe632564812e0a05b2a65612b90"},{"sha":"20c9749b5ed9ecc4ce4631f14639007d36040284","author":{"email":"bcb9ee19c6091ae3933290f91179ddd82d15e2f0@intel.com","name":"chunyang.dai"},"message":"X87: [builtins] Unify the various versions of [[Call]] with a Call builtin.\n\nport ccbb4ff00f1d8f32fd9227cd7aba1723791e5744 (r30629)\n\noriginal commit message:\n\n    The new Call and CallFunction builtins supersede the current\n    CallFunctionStub (and CallIC magic) and will be the single bottleneck\n    for all calling, including the currently special Function.prototype.call\n    and Function.prototype.apply builtins, which had handwritten (and\n    not fully compliant) versions of CallFunctionStub, and also the\n    CallIC(s), which where also slightly different.\n\n    This also reduces the overhead for API function calls, which is still\n    unnecessary high, but let's do that step-by-step.\n\n    This also fixes a bunch of cases where the implicit ToObject for\n    sloppy receivers was done in the wrong context (in the caller\n    context instead of the callee context), which basically meant\n    that we allowed cross context access to %ObjectPrototype%.\n\nBUG=\n\nReview URL: https://codereview.chromium.org/1332703002\n\nCr-Commit-Position: refs/heads/master@{#30668}","distinct":false,"url":"https://api.github.com/repos/v8/v8-git-mirror/commits/20c9749b5ed9ecc4ce4631f14639007d36040284"},{"sha":"99f0130782a57a9abcaea7da5f2a495fe3cb2071","author":{"email":"bcb9ee19c6091ae3933290f91179ddd82d15e2f0@intel.com","name":"chunyang.dai"},"message":"X87: [calls] Consistent call protocol for calls.\n\nport b37907ff7f866873ddfbfc97670b43c19a5fc7f9 (r30648).\n\noriginal commit message:\n\n    The number of actual arguments should always be available, there's no\n    point in trying to optimize away a simple assignment of an immediate to\n    a register before some calls.\n\n    The main motivation is to have a consistent state at the beginning of every\n    function. Currently the arguments register (i.e. rax or eax) either contains\n    the number of arguments or some random garbage depending on whether\n    the callsite decided that the callee might need the information or not.\n    This causes trouble with runtime implementations of functions that\n    do not set internal_formal_parameter_count to the DontAdaptArguments\n    sentinel (we don't have any of those yet), but also makes it impossible\n    to sanity check the arguments in the callee, because the callee doesn't\n    know whether the caller decided to pass the number of arguments or\n    random garbage.\n\nBUG=\n\nReview URL: https://codereview.chromium.org/1335453002\n\nCr-Commit-Position: refs/heads/master@{#30669}","distinct":false,"url":"https://api.github.com/repos/v8/v8-git-mirror/commits/99f0130782a57a9abcaea7da5f2a495fe3cb2071"},{"sha":"9e05ee74467e9ee14e53452f719782b5fe73d92d","author":{"email":"7383d70630fa57abe78d2b74565b5943cae8212b@imgtec.com","name":"Djordje.Pesic"},"message":"MIPS: Fix illegal use of at register\n\nFix illegal use of at register when ldc1 and sdc1 are called. Added dchecks to prevent such a usage.\n\nTEST=mjsunit/asm/float64array-negative-offset(r6), mjsunit/asm/float64array-outofbounds(r6)\n\nReview URL: https://codereview.chromium.org/1323763002\n\nCr-Commit-Position: refs/heads/master@{#30670}","distinct":false,"url":"https://api.github.com/repos/v8/v8-git-mirror/commits/9e05ee74467e9ee14e53452f719782b5fe73d92d"},{"sha":"6b3c070db6e1e2e631f265410f540ec1a6df92ee","author":{"email":"024a1e0af501338d11c3b837c6193d11c140d792@chromium.org","name":"bmeurer"},"message":"[runtime] Sanitize %NewClosure runtime entries.\n\nThere are now two runtime entries %NewClosure and %NewClosure_Tenured,\nwith the same signature (one parameter, the SharedFunctionInfo, and the\ncontext of the caller).\n\nAlso remove the HFunctionLiteral special case instruction from Crankshaft,\nas HCallWithDescriptor with FastNewClosureStub or HCallRuntime with\neither %NewClosure or %NewClosure_Tenured can easily do that for you.\n\nAlso remove the redundant context parameter from the JSCreateClosure\noperator, because every JS operator already takes a context input.\n\nCQ_INCLUDE_TRYBOTS=tryserver.v8:v8_linux_nosnap_dbg\n\nReview URL: https://codereview.chromium.org/1329293003\n\nCr-Commit-Position: refs/heads/master@{#30671}","distinct":false,"url":"https://api.github.com/repos/v8/v8-git-mirror/commits/6b3c070db6e1e2e631f265410f540ec1a6df92ee"}]}