- 17 Jan, 2017 7 commits
-
-
rmcilroy authored
Creates an AstStringConstants container which pre-initializes the string constants used by AstValueFactory. This ensures that all AstValueFactories will produce the same AstValue objects for constants, and so they can be used by the BytecodeGenerator without having to pass the AstValueFactory to it, enabling construction off-thread. BUG=v8:5203 Review-Url: https://codereview.chromium.org/2630343002 Cr-Original-Commit-Position: refs/heads/master@{#42381} Committed: https://chromium.googlesource.com/v8/v8/+/d611496b8ed30af787d8668f96b400617c858508 Review-Url: https://codereview.chromium.org/2630343002 Cr-Commit-Position: refs/heads/master@{#42394}
-
rmcilroy authored
A GC could happen when creating the Module string, which would cause the JSModuleNamespace to be seen in an incomplete state. Instead make this string a root object so that we don't need to allocate it during NewJSModuleNamespace construction. BUG=v8:1569 Review-Url: https://codereview.chromium.org/2631223002 Cr-Commit-Position: refs/heads/master@{#42393}
-
machenbach authored
BUG=chromium:667678 NOTRY=true TBR=titzer@chromium.org,bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2633313002 Cr-Commit-Position: refs/heads/master@{#42392}
-
titzer authored
R=jochen@chromium.org BUG= Review-Url: https://codereview.chromium.org/2637923002 Cr-Commit-Position: refs/heads/master@{#42391}
-
clemensh authored
In V8, we always want the pointer alignment to be left, i.e. "Foo* foo" instead of "Foo *foo". R=jochen@chromium.org NOTRY=true Review-Url: https://codereview.chromium.org/2631183002 Cr-Commit-Position: refs/heads/master@{#42390}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/9a3fba5..f55127d Rolling v8/third_party/catapult: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+log/95b3e83..143ba4d TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/2634223002 Cr-Commit-Position: refs/heads/master@{#42389}
-
pan.deng authored
KillFields of an object should remove its cache from all the fields. Currently, the cache in the front field is kept which is not expected. This patch fixes it. Review-Url: https://codereview.chromium.org/2618273002 Cr-Commit-Position: refs/heads/master@{#42388}
-
- 16 Jan, 2017 33 commits
-
-
jyan authored
RotleftAndMask32 is not efficient on s390 R=bjaideep@ca.ibm.com, joransiu@ca.ibm.com BUG= Review-Url: https://codereview.chromium.org/2638813002 Cr-Commit-Position: refs/heads/master@{#42387}
-
machenbach authored
BUG=chromium:673246 NOTRY=true Review-Url: https://codereview.chromium.org/2635923002 Cr-Commit-Position: refs/heads/master@{#42386}
-
bbudge authored
- Adds vmin, vmax for FP and integer vectors, both signed and unsigned. - Regularizes switching logic in disasm and simulator for special codes 4 and 6. - Factors vrecpe, vrsqrte, vrecps, vrsqrts into helper fns. LOG=N BUG=v8:4124 Review-Url: https://codereview.chromium.org/2623993006 Cr-Commit-Position: refs/heads/master@{#42385}
-
rossberg authored
R=titzer@chromium.org BUG=v8:5840 Review-Url: https://codereview.chromium.org/2633153002 Cr-Commit-Position: refs/heads/master@{#42384}
-
hpayer authored
BUG=v8:5829 patch from issue 2634493004 at patchset 20001 (http://crrev.com/2634493004#ps20001) Review-Url: https://codereview.chromium.org/2634033003 Cr-Commit-Position: refs/heads/master@{#42383}
-
rmcilroy authored
Revert of [Parser] Introduce AstStringConstants to share constants across AstValueFactory (patchset #4 id:80001 of https://codereview.chromium.org/2630343002/ ) Reason for revert: Seems to break modules-namespace2 on gcstress. Original issue's description: > [Parser] Introduce AstStringConstants to share constants across AstValueFactory > > Creates an AstStringConstants container which pre-initializes the > string constants used by AstValueFactory. This ensures that all > AstValueFactories will produce the same AstValue objects for constants, > and so they can be used by the BytecodeGenerator without having to pass > the AstValueFactory to it, enabling construction off-thread. > > BUG=v8:5203 > > Review-Url: https://codereview.chromium.org/2630343002 > Cr-Commit-Position: refs/heads/master@{#42381} > Committed: https://chromium.googlesource.com/v8/v8/+/d611496b8ed30af787d8668f96b400617c858508 TBR=ahaas@chromium.org,marja@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:5203 Review-Url: https://codereview.chromium.org/2638783002 Cr-Commit-Position: refs/heads/master@{#42382}
-
rmcilroy authored
Creates an AstStringConstants container which pre-initializes the string constants used by AstValueFactory. This ensures that all AstValueFactories will produce the same AstValue objects for constants, and so they can be used by the BytecodeGenerator without having to pass the AstValueFactory to it, enabling construction off-thread. BUG=v8:5203 Review-Url: https://codereview.chromium.org/2630343002 Cr-Commit-Position: refs/heads/master@{#42381}
-
clemensh authored
Our .clang-format is derived on the Google style, which sets PointerAlignment to left (e.g. "Type* name"), but sets DerivePointerAlignment to true. Once we started with the wrong style, this made all new code in wasm-debug.cc use PointerAlignment=right, resulting in lots of code using the wrong style. For this CL, I ran clang-format -style="{DerivePointerAlignment: false, BasedOnStyle: \ Google}" -i src/wasm/wasm-debug.cc R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2635003002 Cr-Commit-Position: refs/heads/master@{#42380}
-
rossberg authored
R=titzer@chromium.org BUG= Review-Url: https://codereview.chromium.org/2625133005 Cr-Commit-Position: refs/heads/master@{#42379}
-
daniel.bevenius authored
BUG= Review-Url: https://codereview.chromium.org/2187383002 Cr-Commit-Position: refs/heads/master@{#42378}
-
leszeks authored
BUG=v8:5832 Review-Url: https://codereview.chromium.org/2627783008 Cr-Commit-Position: refs/heads/master@{#42377}
-
ishell authored
NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review-Url: https://codereview.chromium.org/2636893002 Cr-Commit-Position: refs/heads/master@{#42376}
-
yangguo authored
TBR=tebbi@chromium.org BUG=chromium:679841 Review-Url: https://codereview.chromium.org/2631163002 Cr-Commit-Position: refs/heads/master@{#42375}
-
franzih authored
Remove now obsolete constants (see https://chromium.googlesource.com/v8/v8/+/8f0bf07b504e8bb27ef3703388c4c0699670331f) from postmortem metadata generator. BUG= Review-Url: https://codereview.chromium.org/2636863004 Cr-Commit-Position: refs/heads/master@{#42374}
-
mic.besace authored
third_party/inspector_protocol is tracked in git and ignoring it causes problems if the tree is copied to another git repository (e.g. Node.js) Similarly, third_party/binutils has some files checked in. This adds a .gitignore file in this directory (same as Chromium). R=franzih@chromium.org,ofrobots@google.com,machenbach@chromium.org BUG= Review-Url: https://codereview.chromium.org/2635483002 Cr-Commit-Position: refs/heads/master@{#42373}
-
rossberg authored
R=titzer@chromium.org BUG=v8:5818 Review-Url: https://codereview.chromium.org/2637703004 Cr-Commit-Position: refs/heads/master@{#42372}
-
machenbach authored
Continuation of: https://codereview.chromium.org/2620343005/ This removes usage of metadata files entirely. Instead we extract the instrumentation about source files from the test cases. This also adds extra output of the original source file in the detailed failure text for easier debugging. The hashes alone made it hard to reason. BUG=chromium:673246 NOTRY=true TBR=tandrii@chromium.org,mbarbella@chromium.org Review-Url: https://codereview.chromium.org/2634743004 Cr-Commit-Position: refs/heads/master@{#42371}
-
rossberg authored
R=titzer@chromium.org BUG=680833 Review-Url: https://codereview.chromium.org/2634963002 Cr-Commit-Position: refs/heads/master@{#42370}
-
ishell authored
... and ensure that we do a full store when we overwrite uninitialized values. This cleanup is necessary for checking that constant field tracking works as expected (once landed). BUG=v8:5495 Review-Url: https://codereview.chromium.org/2631123002 Cr-Commit-Position: refs/heads/master@{#42369}
-
marja authored
- Generalize the sloppy block function data structures to allow PreParser adding and hoisting sloppy block funcs. - This completes PreParser scope analysis. BUG=v8:5501, v8:5516 R=verwaest@chromium.org Review-Url: https://codereview.chromium.org/2636543002 Cr-Commit-Position: refs/heads/master@{#42368}
-
leszeks authored
Adds checks to ensure that AST rewriting only runs for top-level (or eval) code, that for these cases it runs on the main thread, and that for non-top-level code it can safely be called off-thread. BUG=v8:5832 Review-Url: https://codereview.chromium.org/2630563002 Cr-Commit-Position: refs/heads/master@{#42367}
-
ishell authored
Now we can add a constness bit to the PropertyDetails. BUG=v8:5495 Review-Url: https://codereview.chromium.org/2629423002 Cr-Commit-Position: refs/heads/master@{#42366}
-
bmeurer authored
BUG=chromium:679378 R=jarin@chromium.org Review-Url: https://codereview.chromium.org/2634953002 Cr-Commit-Position: refs/heads/master@{#42365}
-
yangguo authored
R=tebbi@chromium.org BUG=chromium:679841 Review-Url: https://codereview.chromium.org/2638733002 Cr-Commit-Position: refs/heads/master@{#42364}
-
ahaas authored
Without the end opcode at the end of a function nearly every fuzzer input would be invalid and test nothing. R=titzer@chromium.org Review-Url: https://codereview.chromium.org/2634943002 Cr-Commit-Position: refs/heads/master@{#42363}
-
leszeks authored
Moves constant element/property array building to be deferred for igition and on-demand for the other compilers, and splits off the object/array literal depth/flag initialisation from the array building. BUG=v8:5832 Review-Url: https://codereview.chromium.org/2625873009 Cr-Commit-Position: refs/heads/master@{#42362}
-
jochen authored
BUG=v8:5215 R=rmcilroy@chromium.org,hpayer@chromium.org,vogelheim@chromium.org,marja@chromium.org Review-Url: https://codereview.chromium.org/2625413004 Cr-Commit-Position: refs/heads/master@{#42361}
-
ishell authored
BUG=v8:5495 Review-Url: https://codereview.chromium.org/2628323003 Cr-Commit-Position: refs/heads/master@{#42360}
-
ahaas authored
The special treatment is not required anymore because the wasm spec changed and NaNs do not have to be preserved anymore. In addition, it may introduce non-determinism which confused the fuzzers. R=titzer@chromium.org BUG=chromium:681033 Review-Url: https://codereview.chromium.org/2630293002 Cr-Commit-Position: refs/heads/master@{#42359}
-
predrag.rudic authored
BUG= Review-Url: https://codereview.chromium.org/2398993003 Cr-Commit-Position: refs/heads/master@{#42358}
-
marja authored
src/ast/scopeinfo.cc -> src/objects/scope-info.cc BUG=v8:5402 Review-Url: https://codereview.chromium.org/2637793002 Cr-Commit-Position: refs/heads/master@{#42357}
-
machenbach authored
BUG=chromium:663750,chromium:662907,chromium:663340,chromium:666308,chromium:669017 NOTRY=true TBR=jarin@chromium.org, bmeurer@chromium.org Review-Url: https://codereview.chromium.org/2632153002 Cr-Commit-Position: refs/heads/master@{#42356}
-
gdeepti authored
BUG=5823 R=bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2636803002 Cr-Commit-Position: refs/heads/master@{#42355}
-