- 07 Oct, 2016 35 commits
-
-
kozyatinskiy authored
String16 is not public part of src/inspector. All usage are replaced with vector of char/unit16_t to avoid potential linker problems. BUG=chromium:635948 R=dgozman@chromium.org,machenbach@chromium.org Review-Url: https://codereview.chromium.org/2403493002 Cr-Commit-Position: refs/heads/master@{#40098}
-
hablich authored
Revert of [parser] Deprecate ParseInfo constructor taking closure. (patchset #2 id:20001 of https://codereview.chromium.org/2396963003/ ) Reason for revert: Needed to revert https://codereview.chromium.org/2400343002/ Original issue's description: > [parser] Deprecate ParseInfo constructor taking closure. > > This removes the {ParseInfo} constructor consuming a closure, replacing > all uses to pass only the shared function info. The goal is to make the > fact that parsing is independent of a concrete closure explicit. > > R=jochen@chromium.org > BUG=v8:2206 > > Committed: https://crrev.com/3de42b3f224217ec88e4c609d3cf23fe06806dca > Cr-Commit-Position: refs/heads/master@{#40083} TBR=jochen@chromium.org,bmeurer@chromium.org,marja@chromium.org,yangguo@chromium.org,mstarzinger@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:2206 Review-Url: https://codereview.chromium.org/2406623002 Cr-Commit-Position: refs/heads/master@{#40097}
-
neis authored
This implements namespace imports (import * as foo from "bar"), except for the @@iterator property on namespace objects (to be done later). R=adamk@chromium.org BUG=v8:1569 Review-Url: https://codereview.chromium.org/2388153003 Cr-Commit-Position: refs/heads/master@{#40096}
-
adamk authored
Both bits of code were pointed out by our test coverage tools. R=gsathya@chromium.org Review-Url: https://codereview.chromium.org/2394403002 Cr-Commit-Position: refs/heads/master@{#40095}
-
jbroman authored
Found with libfuzzer. The length is automatically converted to int (thus large sizes could become negative, even though they are legal "array sizes"). Besides that, the length is coerced to a SMI (which is an even tighter constraint on 32-bit systems, where it limits the legal sizes to 2^30 - 1). Add checks that the length of a dense array is below that threshold, and also fail fast if a length that is provided obviously could not be the correct dense length (because there isn't enough data left in the buffer to populate such an array). BUG=chromium:148757 Review-Url: https://codereview.chromium.org/2399873002 Cr-Commit-Position: refs/heads/master@{#40094}
-
petermarshall authored
BUG=v8:5364 Review-Url: https://codereview.chromium.org/2350963004 Cr-Commit-Position: refs/heads/master@{#40093}
-
bjaideep authored
Port ec132e05 Original commit message: (GcStress failure was unrelated.) At one time, we hoped to generate the same code for different native contexts. But in truth, much performance comes from optimizing on the native context. Now we abandon this pathway. R=mvstanton@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/2401043002 Cr-Commit-Position: refs/heads/master@{#40092}
-
machenbach authored
BUG=v8:5451,v8:5496 TBR=mtrofin@chromium.org, titzer@chromium.org, ahaas@chromium.org NOTRY=true NOTREECHECKS=true Review-Url: https://codereview.chromium.org/2399343003 Cr-Commit-Position: refs/heads/master@{#40091}
-
rmcilroy authored
A wide jump can be patched with a non-wide jump target operand, so the DCHECK added in r39637 was wrong. BUG=chromium:652430 Review-Url: https://codereview.chromium.org/2400203002 Cr-Commit-Position: refs/heads/master@{#40090}
-
mstarzinger authored
This removes the restriction of only allowing lazy compilation for top-level eval code with a context. We can by now compile such code without a concrete closure. R=yangguo@chromium.org Review-Url: https://codereview.chromium.org/2400973002 Cr-Commit-Position: refs/heads/master@{#40089}
-
jbroman authored
Previously this would result in applying trying to find a size modulo zero, which causes SIGFPE. This approach was preferred over adding a default case to preserve the ability of the compiler to detect unhandled switch cases (within the valid range of the enum). BUG=chromium:148757 Review-Url: https://codereview.chromium.org/2395073003 Cr-Commit-Position: refs/heads/master@{#40088}
-
jgruber authored
BUG= Committed: https://crrev.com/7db0ecdec3cf330766575cb7973b983f3f1e3020 Review-Url: https://codereview.chromium.org/2381843002 Cr-Original-Commit-Position: refs/heads/master@{#40080} Cr-Commit-Position: refs/heads/master@{#40087}
-
Mike Stanton authored
(GcStress failure was unrelated.) At one time, we hoped to generate the same code for different native contexts. But in truth, much performance comes from optimizing on the native context. Now we abandon this pathway. BUG= TBR=bmeurer@chromium.org NOPRESUBMIT=true NOTREECHECKS=true Review URL: https://codereview.chromium.org/2402663002 . Cr-Commit-Position: refs/heads/master@{#40086}
-
danno authored
In the process, also fix a merge hiccup that clobbered https://codereview.chromium.org/2003663002/ back in May. BUG=chromium:608675 LOG=N Review-Url: https://codereview.chromium.org/2397223002 Cr-Commit-Position: refs/heads/master@{#40085}
-
machenbach authored
The create.js file is loaded unconditionally in run.js, therefore we need to add it to resources, otherwise it fails on Android. TBR=caitp@igalia.com NOTRY=true Review-Url: https://codereview.chromium.org/2401883002 Cr-Commit-Position: refs/heads/master@{#40084}
-
mstarzinger authored
This removes the {ParseInfo} constructor consuming a closure, replacing all uses to pass only the shared function info. The goal is to make the fact that parsing is independent of a concrete closure explicit. R=jochen@chromium.org BUG=v8:2206 Review-Url: https://codereview.chromium.org/2396963003 Cr-Commit-Position: refs/heads/master@{#40083}
-
jgruber authored
This reverts commit 7db0ecde. Manual revert since automatic revert is too large for the web interface. BUG= TBR=bmeurer@chromium.org,mstarzinger@chromium.org,yangguo@chromium.org,ahaas@chromium.org NOPRESUBMIT=true NOTREECHECKS=true Review-Url: https://codereview.chromium.org/2396353002 Cr-Commit-Position: refs/heads/master@{#40082}
-
mvstanton authored
Revert of [turbofan] Discard the shared code entry in the optimized code map. (patchset #3 id:40001 of https://codereview.chromium.org/2401653002/ ) Reason for revert: Possible GCSTRESS failure, investigating. Original issue's description: > [turbofan] Discard the shared code entry in the optimized code map. > > At one time, we hoped to generate the same code for different > native contexts. But in truth, much performance comes from optimizing > on the native context. Now we abandon this pathway. > > BUG= > > Committed: https://crrev.com/55af3c44c99a6e4cd6d53df775023d760ad2b2c3 > Cr-Commit-Position: refs/heads/master@{#40079} TBR=mstarzinger@chromium.org,ishell@chromium.org,bmeurer@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review-Url: https://codereview.chromium.org/2403453002 Cr-Commit-Position: refs/heads/master@{#40081}
-
jgruber authored
BUG= Review-Url: https://codereview.chromium.org/2381843002 Cr-Commit-Position: refs/heads/master@{#40080}
-
mvstanton authored
At one time, we hoped to generate the same code for different native contexts. But in truth, much performance comes from optimizing on the native context. Now we abandon this pathway. BUG= Review-Url: https://codereview.chromium.org/2401653002 Cr-Commit-Position: refs/heads/master@{#40079}
-
neis authored
The _ParseException function in testcfg.py made incorrect assumptions about how exceptions are printed (I believe it expected a trace like that produced by Error). R=littledan@chromium.org BUG=v8:5136 Review-Url: https://codereview.chromium.org/2386103010 Cr-Commit-Position: refs/heads/master@{#40078}
-
clemensh authored
In CreateModuleObjectFromBytes, pointers to the raw bytes will be stored inside the decoded WasmModule, and still used after allocating V8 stuff in WasmModule::CompileFunctions. We thus cannot pass a raw pointer to the V8 heap. Fix this by copying the bytes before decoding. R=mtrofin@chromium.org, titzer@chromium.org Review-Url: https://codereview.chromium.org/2402633002 Cr-Commit-Position: refs/heads/master@{#40077}
-
titzer authored
R=mtrofin@chromium.org,gdeepti@chromium.org BUG=chromium:575167 Review-Url: https://codereview.chromium.org/2392943006 Cr-Commit-Position: refs/heads/master@{#40076}
-
hpayer authored
BUG=chromium:648568 Review-Url: https://codereview.chromium.org/2397373002 Cr-Commit-Position: refs/heads/master@{#40075}
-
jochen authored
For now keep the logic in compiler.cc and add a DCHECK that the scopes and compiler.cc agree. Use this knowledge to only created ScopeInfos for literals we'll actually compile. BUG=v8:5394,v8:5422 R=marja@chromium.org,verwaest@chromium.org Review-Url: https://codereview.chromium.org/2399833002 Cr-Commit-Position: refs/heads/master@{#40074}
-
bmeurer authored
R=mvstanton@chromium.org BUG=v8:5267 Review-Url: https://codereview.chromium.org/2397253002 Cr-Commit-Position: refs/heads/master@{#40073}
-
bmeurer authored
This implicitly convers parseFloat on the global object as well, since it's the same function. This is mostly straight-forward, but adds another fast case for HeapNumbers as well. R=ishell@chromium.org Review-Url: https://codereview.chromium.org/2395373002 Cr-Commit-Position: refs/heads/master@{#40072}
-
clemensh authored
Revert of [esnext] ship String.prototype.padStart / String.prototype.padEnd (patchset #1 id:1 of https://codereview.chromium.org/2382193002/ ) Reason for revert: Causes several GC bugs, e.g. https://build.chromium.org/p/client.v8.ports/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20gc%20stress/builds/2858/steps/Mjsunit/logs/debug-constructed-by Original issue's description: > [esnext] ship String.prototype.padStart / String.prototype.padEnd > > Enable the --harmony-string-padding flag by default > > BUG=v8:4954 > R=adamk@chromium.org, littledan@chromium.org > > Committed: https://crrev.com/8352a0feaccfd9a19f3b38564ed2c0859dd6e3d5 > Cr-Commit-Position: refs/heads/master@{#40060} TBR=littledan@chromium.org,adamk@chromium.org,foolip@chromium.org,caitp@igalia.com # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:4954 Review-Url: https://codereview.chromium.org/2398183003 Cr-Commit-Position: refs/heads/master@{#40071}
-
mstarzinger authored
R=marja@chromium.org Review-Url: https://codereview.chromium.org/2392303004 Cr-Commit-Position: refs/heads/master@{#40070}
-
neis authored
R=adamk@chromium.org BUG= Review-Url: https://codereview.chromium.org/2394173002 Cr-Commit-Position: refs/heads/master@{#40069}
-
jochen authored
Reland of land "Turn libbase into a component" (patchset #1 id:1 of https://codereview.chromium.org/2396933002/ ) Reason for revert: let's see whether it sticks this time Original issue's description: > Revert of Reland "Turn libbase into a component" (patchset #1 id:1 of https://codereview.chromium.org/2395553002/ ) > > Reason for revert: > Speculative revert due to very strange-looking win/dbg failures > which reference SignedDivisionByConstant: > > https://build.chromium.org/p/client.v8/builders/V8%20Win64%20-%20debug/builds/12736 > > Original issue's description: > > Reland "Turn libbase into a component" > > > > Original issue's description: > > > Turn libbase into a component > > > > > > This is a precondition for turning libplatform into a component > > > > > > BUG=v8:5412 > > > R=jgruber@chromium.org,machenbach@chromium.org > > > CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_compile_ > > dbg_ng;master.tryserver.chromium.android:android_clang_dbg_recipe > > > > > > Committed: https://crrev.com/614e615775f732d71b5ee94ed29737d8de687104 > > > Cr-Commit-Position: refs/heads/master@{#39950} > > > > BUG=v8:5412 > > TBR=jgruber@chromium.org,machenbach@chromium.org > > CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_compile_dbg_ng;master.tryserver.chromium.android:android_clang_dbg_recipe;master.tryserver.chromium.mac:mac_chromium_compile_dbg_ng > > > > Committed: https://crrev.com/17cb51254cafa932025e9980b60f89f756d411cb > > Cr-Commit-Position: refs/heads/master@{#39969} > > TBR=jgruber@chromium.org,machenbach@chromium.org,jochen@chromium.org > # Skipping CQ checks because original CL landed less than 1 days ago. > NOPRESUBMIT=true > NOTREECHECKS=true > NOTRY=true > BUG=v8:5412 > > Committed: https://crrev.com/e75b9f6ed5da39e6c7a8d70cf48afbc9958afc85 > Cr-Commit-Position: refs/heads/master@{#40009} TBR=jgruber@chromium.org,machenbach@chromium.org,adamk@chromium.org # Not skipping CQ checks because original CL landed more than 1 days ago. BUG=v8:5412 Review-Url: https://codereview.chromium.org/2399323002 Cr-Commit-Position: refs/heads/master@{#40068}
-
gdeepti authored
- Added gating code in the module-decoder to allow SIMD code only when it can be decoded correctly - SIMD128 values should not be exported to JS - Try/Catch should not be available in asmjs modules - Trivial fixes for S128 values BUG=chromium:648079 R=ahaas@chromium.org, titzer@chromium.org, bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2400863003 Cr-Commit-Position: refs/heads/master@{#40067}
-
jwolfe authored
Review-Url: https://codereview.chromium.org/2399933005 Cr-Commit-Position: refs/heads/master@{#40066}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/67604e1..792a87c Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clan/+log/1f92f99..30c5a8b TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/2393083006 Cr-Commit-Position: refs/heads/master@{#40065}
-
kozyatinskiy authored
Only subset of internal properties can be useful in preview, report only them. BUG=chromium:653610 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2399003003 Cr-Commit-Position: refs/heads/master@{#40064}
-
- 06 Oct, 2016 5 commits
-
-
mtrofin authored
Strongly typing module_bytes needs a patch for the serialization code. Serialization bypasses module bytes, so their presence can't be compulsory. BUG= Review-Url: https://codereview.chromium.org/2397303002 Cr-Commit-Position: refs/heads/master@{#40063}
-
clemensh authored
Use information in the WasmCompiledModule instead. R=titzer@chromium.org,mtrofin@chromium.org Review-Url: https://codereview.chromium.org/2396043002 Cr-Commit-Position: refs/heads/master@{#40062}
-
clemensh authored
I am removing three fields from the wasm object in a follow-up commit, and using information in the compiled module instead. In order to not weaken the verification, this commit adds appropriate checks on the compiled module. R=titzer@chromium.org,mtrofin@chromium.org Review-Url: https://codereview.chromium.org/2394663008 Cr-Commit-Position: refs/heads/master@{#40061}
-
caitp authored
Enable the --harmony-string-padding flag by default BUG=v8:4954 R=adamk@chromium.org, littledan@chromium.org Review-Url: https://codereview.chromium.org/2382193002 Cr-Commit-Position: refs/heads/master@{#40060}
-
ziyang authored
Port 0c168a90 R=tebbi@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, bjaideep@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com BUG= Review-Url: https://codereview.chromium.org/2397193003 Cr-Commit-Position: refs/heads/master@{#40059}
-