- 25 Jul, 2016 1 commit
-
-
jarin authored
BUG=chromium:630611 Review-Url: https://codereview.chromium.org/2177483002 Cr-Commit-Position: refs/heads/master@{#37994}
-
- 23 Jul, 2016 3 commits
-
-
cbruni authored
In PrependElementIndicesImpl we sort a FixedArray of indices potentially containing HeapNumbers. During the string conversion we might trigger a GC. This in turn might try to read a slot where we previously had a HeapNumber but the sort sneaked a SMI in there which is not a valid pointer. BUG=chromium:630561 Review-Url: https://codereview.chromium.org/2173653003 Cr-Commit-Position: refs/heads/master@{#37993}
-
v8-autoroll authored
Rolling v8/build to 2c67d4d74b6b3673228fab191918500a582ef3b0 Rolling v8/third_party/android_tools to e4d61eb8f463e6cb8d1e1269a15c22f7c9bbd122 Rolling v8/tools/clang to 496622ab4aaa5be7e5a9b80617013cb02f45dc87 Rolling v8/tools/mb to 0c4dc43c454f26936ddf3074ab8e9a41e3dc03a3 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/2173293002 Cr-Commit-Position: refs/heads/master@{#37992}
-
bjaideep authored
Port ba092fb0 Original commit message: So far we don't have a useful way to inline Math.max or Math.min in TurboFan optimized code. This adds new operators NumberMax and NumberMin and changes the Float64Max/Float64Min operators to have JavaScript semantics instead of the C++ semantics that it had previously. This also removes support for recognizing the tenary case in the CommonOperatorReducer, since that doesn't seem to have any positive impact (and actually doesn't show up in regular JavaScript, where people use Math.max/Math.min instead). Drive-by-fix: Also nuke the unused Float32Max/Float32Min operators. R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com BUG= LOG=N Review-Url: https://codereview.chromium.org/2179503003 Cr-Commit-Position: refs/heads/master@{#37991}
-
- 22 Jul, 2016 32 commits
-
-
adamk authored
The uses_arguments() bool is not needed for correct behavior, since that same information is available after scope analysis based on whether we allocated the Scope::arguments_ var. BUG=v8:5209 Review-Url: https://codereview.chromium.org/2168293002 Cr-Commit-Position: refs/heads/master@{#37990}
-
adamk authored
This replaces the AstVisitor approach for scope rewriting with a Scope-only solution, using a new Scope::Snapshot object that keeps track of inner scopes, unresolved variables, and temps. The only use of the AstVisitor is now for parameter varblock scopes introduced due to sloppy eval in parameters, which greatly simplifies the rewriter as it no longer needs to handle temps. A future CL may be able to eliminate it altogether by taking a snapshot per function argument. Based on verwaest's https://codereview.chromium.org/2166023002/. BUG=v8:5226 Review-Url: https://codereview.chromium.org/2171703004 Cr-Commit-Position: refs/heads/master@{#37989}
-
ivica.bogosavljevic authored
Implement UnalignedLoad and UnalignedStore optional turbofan operators and use them in WasmCompiler for unaligned memory access. BUG= Review-Url: https://codereview.chromium.org/2122853002 Cr-Commit-Position: refs/heads/master@{#37988}
-
caitp authored
BUG=v8:5134 R=cbruni@chromium.org, littledan@chromium.org, neis@chromium.org Review-Url: https://codereview.chromium.org/2131383002 Cr-Commit-Position: refs/heads/master@{#37987}
-
mark authored
This reverts commit 31388627. BUG=chromium:630629 Review-Url: https://codereview.chromium.org/2171373002 Cr-Commit-Position: refs/heads/master@{#37986}
-
littledan authored
TC-39 recently decided to remove the Python-based testing harness from the Test262 project [1]. The code has been duplicated in a standalone project; update V8's dependencies to fetch from that new location. This is based on an earlier patch by Mike Pennisi. [1] https://github.com/tc39/tc39-notes/blob/2b9722db9b90011d6083a5f1c8ff1559cbe01c0b/es7/2016-05/may-25.md BUG=v8:5078 Review-Url: https://codereview.chromium.org/2131743002 Cr-Commit-Position: refs/heads/master@{#37985}
-
vogelheim authored
Revert of Re-land "Fix double-building of v8 in GN builds" (patchset #2 id:20001 of https://codereview.chromium.org/2171083003/ ) Reason for revert: Reverted, because it breaks some funky android build. Can reproduce breakage locally, w/ args.gn as follows: disable_brotli_filter = true disable_file_support = true disable_ftp_support = true enable_websockets = false ffmpeg_branding = "Chrome" is_component_build = false is_debug = true proprietary_codecs = true symbol_level = 1 target_cpu = "x86" target_os = "android" use_goma = true use_platform_icu_alternatives = true This ends up building the mkpeephole tool w/ an architecture that won't run on the build machine. Original issue's description: > Re-land "Fix double-building of v8 in GN builds" > > This re-lands r37926 w/ the needed fix for cross-compiles; we > can only re-use the default toolchain when the host can actually > run it. > > R=machenbach@chromium.org > BUG=629825 > > Committed: https://crrev.com/5b762044b53f988fa9a534fe1a84f9938b3abd75 > Cr-Commit-Position: refs/heads/master@{#37970} TBR=machenbach@chromium.org,dpranke@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=629825 Review-Url: https://codereview.chromium.org/2175693003 Cr-Commit-Position: refs/heads/master@{#37984}
-
ishell authored
BUG=chromium:619016 Review-Url: https://codereview.chromium.org/2139373002 Cr-Commit-Position: refs/heads/master@{#37983}
-
jochen authored
TBR=machenbach@chromium.org BUG= Review-Url: https://codereview.chromium.org/2174613003 Cr-Commit-Position: refs/heads/master@{#37982}
-
cbruni authored
BUG= Review-Url: https://codereview.chromium.org/2163823004 Cr-Commit-Position: refs/heads/master@{#37981}
-
jochen authored
Next step will be to add methods for parsing and then compiling. BUG=v8:5215 R=marja@chromium.org Review-Url: https://codereview.chromium.org/2171323002 Cr-Commit-Position: refs/heads/master@{#37980}
-
jochen authored
BUG= R=hpayer@chromium.org Review-Url: https://codereview.chromium.org/2171313002 Cr-Commit-Position: refs/heads/master@{#37979}
-
jgruber authored
BUG=v8:5216 R=yangguo@chromium.org Review-Url: https://codereview.chromium.org/2175603003 Cr-Commit-Position: refs/heads/master@{#37978}
-
yangguo authored
This is not in use yet, but will be soon. R=jochen@chromium.org, machenbach@chromium.org BUG=chromium:580337 Review-Url: https://codereview.chromium.org/2175653002 Cr-Commit-Position: refs/heads/master@{#37977}
-
klaasb authored
ToNumber's result is always directly stored to a register using a Star bytecode. Fuse it into ToNumber. BUG=v8:4280 LOG=n Review-Url: https://codereview.chromium.org/2165953002 Cr-Commit-Position: refs/heads/master@{#37976}
-
jgruber authored
Review-Url: https://codereview.chromium.org/2158303002 Cr-Commit-Position: refs/heads/master@{#37975}
-
jgruber authored
This will get a new call site in an upcoming commit, move it to String so it's accessible from without runtime-strings.cc. BUG= Review-Url: https://codereview.chromium.org/2176553002 Cr-Commit-Position: refs/heads/master@{#37974}
-
rmcilroy authored
The effect control linearizer runs off-thread and needs the ToNumber call descriptor. Add a hack to create this on the main thread to ensure off-thread's don't race on it's construction. Also add a DCHEK to the CallInterfaceDescriptor to ensure they are always initilaized on the main thread. Review-Url: https://codereview.chromium.org/2168843003 Cr-Commit-Position: refs/heads/master@{#37973}
-
hablich authored
The auto-tag bot removes the need to handle version changes in each merge individually. As a result this 'feature' is removed. BUG=v8:4408 R=machenbach@chromium.org LOG=N NOTRY=true Review-Url: https://codereview.chromium.org/1398033003 Cr-Commit-Position: refs/heads/master@{#37972}
-
bmeurer authored
So far we don't have a useful way to inline Math.max or Math.min in TurboFan optimized code. This adds new operators NumberMax and NumberMin and changes the Float64Max/Float64Min operators to have JavaScript semantics instead of the C++ semantics that it had previously. This also removes support for recognizing the tenary case in the CommonOperatorReducer, since that doesn't seem to have any positive impact (and actually doesn't show up in regular JavaScript, where people use Math.max/Math.min instead). Drive-by-fix: Also nuke the unused Float32Max/Float32Min operators. R=jarin@chromium.org Review-Url: https://codereview.chromium.org/2170343002 Cr-Commit-Position: refs/heads/master@{#37971}
-
dpranke authored
This re-lands r37926 w/ the needed fix for cross-compiles; we can only re-use the default toolchain when the host can actually run it. R=machenbach@chromium.org BUG=629825 Review-Url: https://codereview.chromium.org/2171083003 Cr-Commit-Position: refs/heads/master@{#37970}
-
jgruber authored
This allows us to skip complicated logic for setting the accessors. BUG= Review-Url: https://codereview.chromium.org/2164903004 Cr-Commit-Position: refs/heads/master@{#37969}
-
yangguo authored
NOTRY=true TBR=littledan@chromium.org Review-Url: https://codereview.chromium.org/2171233002 Cr-Commit-Position: refs/heads/master@{#37968}
-
hpayer authored
BUG=630386 LOG=n Review-Url: https://codereview.chromium.org/2160613002 Cr-Commit-Position: refs/heads/master@{#37967}
-
yangguo authored
This is in preparation to implementing exception prediction for async functions. Each handler table entry can now predict "caught", "uncaught", or "promise". The latter indicates that the exception will lead to a promise rejection. To mark the relevant try-catch blocks, we add a new native syntax. try { } %catch (e) { } indicates a TryCatchStatement with the "promise" prediction. The previous implementation of using the function to tell the relevant try-catch apart from inner try-catch blocks will not work for async functions since these can have inner try-catch blocks inside the same function. BUG=v8:5167 Review-Url: https://codereview.chromium.org/2161263003 Cr-Commit-Position: refs/heads/master@{#37966}
-
bmeurer authored
We can compute the absolute integer value w/o any conditional execution by using the bit trick formula let sign = input >> 31 in (input ^ sign) - sign which generates fairly decent code on all supported architectures. R=jarin@chromium.org Review-Url: https://codereview.chromium.org/2169293002 Cr-Commit-Position: refs/heads/master@{#37965}
-
v8-autoroll authored
Rolling v8/build to 5782f1c84fc41934d265f69e5bd61badbf61e5c5 Rolling v8/tools/mb to c0f2da01e7e7e530fcbbf3823b7c7655632f05b1 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/2171153002 Cr-Commit-Position: refs/heads/master@{#37964}
-
zhengxing.li authored
port 4b59bf53 (r37934) original commit message: Use the ForInFilterStub directly. Hence we will only jump to the runtime for special receivers (instance_type <= LAST_SPECIAL_RECEIVER_TYPE) and for converting element indices which are not in the string cache. BUG= Review-Url: https://codereview.chromium.org/2176473002 Cr-Commit-Position: refs/heads/master@{#37963}
-
zhengxing.li authored
port 66cb026f (r37929) original commit message: Original message: Calling Runtime::kAbort through a builtin instead of the c-entry stub will allow to generate the call in a background thread, because a builtin provides its own handle, whereas a code stub does not. @v8-mips-ports: Could you take a special look at the padding that is done in MacroAssembler::Abort()? Reason for revert: The reason for reverting is: Blocks roll: https://build.chromium.org/p/client.v8.ports/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20debug/builds/1622 The problem was that on arm64 the builtin for Abort() contained a call to Abort(). The problem is fixed by using a NoUseRealAbortsScope in the code generation of Abort(). BUG= Review-Url: https://codereview.chromium.org/2172093002 Cr-Commit-Position: refs/heads/master@{#37962}
-
ritesht authored
Revert "[wasm] Adding a convolution matrix filter test to highlight the performance advantages of JITing" GC-Stress asserts in filter-jit. This reverts commit ccfd224e. BUG=v8:5044 R=bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2168343002 Cr-Commit-Position: refs/heads/master@{#37961}
-
bjaideep authored
Port 8aeb7439 Fix for ppc file, using macro functions to xor and add to handle the case when kPrimaryMagic/kSecondaryMagic is > 16bits. R=ishell@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com BUG= LOG=N Review-Url: https://codereview.chromium.org/2169183002 Cr-Commit-Position: refs/heads/master@{#37960}
-
jwolfe authored
See discussion in https://codereview.chromium.org/2156303002/#msg8 With the new --harmony-function-tostring behavior, these tests would fail without this change. This change makes the tests pass regardless of whether or not --harmony-function-tostring is used. All of these changes are simply inserting a space after the "function" keyword to match the current function toString behavior. When --harmony-function-tostring is enabled, the toString behavior matches the spacing used in the function declaration. With the declaration matching the current formatting, the toString behavior becomes unaffected by --harmony-function-tostring. BUG=v8:4958 LOG=n Review-Url: https://codereview.chromium.org/2161413002 Cr-Commit-Position: refs/heads/master@{#37959}
-
- 21 Jul, 2016 4 commits
-
-
adamk authored
R=littledan@chromium.org Review-Url: https://codereview.chromium.org/2172723003 Cr-Commit-Position: refs/heads/master@{#37958}
-
ritesht authored
This cl also fixes two bugs in the previous code: 1) JITed functions were not allowed access to the heap because the module instance wasn't correctly synthesized. This wasn't discovered in the previous test. 2) Decoding of functions with the JITSingleFunction opcode was off by 1 as the length of the opcode wasn't computed correctly. BUG=5044 Review-Url: https://codereview.chromium.org/2168183002 Cr-Commit-Position: refs/heads/master@{#37957}
-
bjaideep authored
Port e83739c0 Fix applies to PPC/s390 as well. R=jacob.bramley@arm.com, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com BUG=v8:5214 LOG=N Review-Url: https://codereview.chromium.org/2167273003 Cr-Commit-Position: refs/heads/master@{#37956}
-
ivica.bogosavljevic authored
BUG=v8:5213 Review-Url: https://codereview.chromium.org/2163963003 Cr-Commit-Position: refs/heads/master@{#37955}
-