- 28 Apr, 2016 35 commits
-
-
ivica.bogosavljevic authored
Implement unaligned access instructions, and tests for corresponding instruction BUG= Review-Url: https://codereview.chromium.org/1902743002 Cr-Commit-Position: refs/heads/master@{#35873}
-
neis authored
Instead of replacing the array with an empty one after resuming, overwrite contents with a new Oddball. This will simplify the work to be done by the bytecode graphbuilder and potentially allow for more optimization. (For full-codegen generators, nothing changes.) BUG=v8:4907 LOG=n Review-Url: https://codereview.chromium.org/1923253002 Cr-Commit-Position: refs/heads/master@{#35872}
-
machenbach authored
Revert of [Ignition] Test ignition on all bots. (patchset #4 id:60001 of https://codereview.chromium.org/1804003002/ ) Reason for revert: Will resubmit with proper fix and more test skips. Original issue's description: > [Ignition] Test ignition on all bots. > > This adds ignition to the testing variants that are run on all > bots. > > Failing tests can only be skipped with the NO_IGNITION > keyword in status files. Existing expectations for the > ignition_turbofan variant are all duplicated and use the > NO_IGNITION keyword as well now. > > BUG=v8:4280 > LOG=N > NOTRY=true TBR=rmcilroy@chromium.org,mstarzinger@chromium.org,yangguo@chromium.org,mythria@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:4280 Review-Url: https://codereview.chromium.org/1930943002 Cr-Commit-Position: refs/heads/master@{#35871}
-
yangguo authored
R=vogelheim@chromium.org Review-Url: https://codereview.chromium.org/1928943002 Cr-Commit-Position: refs/heads/master@{#35870}
-
mlippautz authored
Speculatively forcining inlining as not inlining potentially regresses performance. BUG=chromium:605524 LOG=N Review-Url: https://codereview.chromium.org/1924033003 Cr-Commit-Position: refs/heads/master@{#35869}
-
rossberg authored
R=hablich@chromium.org BUG=v8:4942 LOG=true Review-Url: https://codereview.chromium.org/1928513004 Cr-Commit-Position: refs/heads/master@{#35868}
-
balazs.kilvady authored
-Wno-undefined-var-template flag is unknown by Xcode's clang. And it is better to use the same clang version that is used on linux. BUG= Review-Url: https://codereview.chromium.org/1926633004 Cr-Commit-Position: refs/heads/master@{#35867}
-
mmoroz authored
R=aizatsky@chromium.org, jochen@chromium.org, kcc@chromium.org, ochang@chromium.org BUG=584819 LOG=Y Review-Url: https://codereview.chromium.org/1927933002 Cr-Commit-Position: refs/heads/master@{#35866}
-
machenbach authored
This adds ignition to the testing variants that are run on all bots. Failing tests can only be skipped with the NO_IGNITION keyword in status files. Existing expectations for the ignition_turbofan variant are all duplicated and use the NO_IGNITION keyword as well now. BUG=v8:4280 LOG=N NOTRY=true Review-Url: https://codereview.chromium.org/1804003002 Cr-Commit-Position: refs/heads/master@{#35865}
-
yangguo authored
DevTools uses the debug interrupt to trap on function entry. Without source position at the stack check, we would get bogus source positions. R=mstarzinger@chromium.org BUG=chromium:595646 LOG=N Review-Url: https://codereview.chromium.org/1925063002 Cr-Commit-Position: refs/heads/master@{#35864}
-
machenbach authored
Revert of [turbofan] Run everything after representation selection concurrently. (patchset #2 id:20001 of https://codereview.chromium.org/1926023002/ ) Reason for revert: [Sheriff] Flaky crashed here and there: https://build.chromium.org/p/client.v8/builders/V8%20Linux/builds/9867 https://build.chromium.org/p/client.v8/builders/V8%20Linux64/builds/9589 https://build.chromium.org/p/client.v8/builders/V8%20Mac/builds/7679 Original issue's description: > [turbofan] Run everything after representation selection concurrently. > > Further refactor the pipeline to even run the first scheduler (part of > the effect control linearization) concurrently. This temporarily > disables most of the write barrier elimination, but we will get back to > that later. TBR=mstarzinger@chromium.org,bmeurer@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review-Url: https://codereview.chromium.org/1925073002 Cr-Commit-Position: refs/heads/master@{#35863}
-
neis authored
- Move the check from the BytecodeArrayBuilder destructor, which doesn't get called, to the ToBytecodeArray function. - Remove the now empty destructor. - For generators, bind unused resume point labels somewhere. R=rmcilroy@chromium.org BUG= Review-Url: https://codereview.chromium.org/1924093005 Cr-Commit-Position: refs/heads/master@{#35862}
-
bmeurer authored
Further refactor the pipeline to even run the first scheduler (part of the effect control linearization) concurrently. This temporarily disables most of the write barrier elimination, but we will get back to that later. Review-Url: https://codereview.chromium.org/1926023002 Cr-Commit-Position: refs/heads/master@{#35861}
-
machenbach authored
BUG=chromium:606898 LOG=n Review-Url: https://codereview.chromium.org/1932703002 Cr-Commit-Position: refs/heads/master@{#35860}
-
epertoso authored
We effectively have 4 different cases to deal with, including the default, but on some platform where we emit the jump table inline (e.g. arm64) we end up emitting an unconditional jump to the same address 127 times. BUG= Review-Url: https://codereview.chromium.org/1765883002 Cr-Commit-Position: refs/heads/master@{#35859}
-
jochen authored
R=machenbach@chromium.org BUG= Review-Url: https://codereview.chromium.org/1927083002 Cr-Commit-Position: refs/heads/master@{#35858}
-
vogelheim authored
BUG=v8:4947 LOG=Y Review-Url: https://codereview.chromium.org/1919673006 Cr-Commit-Position: refs/heads/master@{#35857}
-
yangguo authored
R=machenbach@chromium.org BUG=v8:4690 LOG=N Review-Url: https://codereview.chromium.org/1925993002 Cr-Commit-Position: refs/heads/master@{#35856}
-
jarin authored
BUG=chromium:607115 LOG=n Review-Url: https://codereview.chromium.org/1928903002 Cr-Commit-Position: refs/heads/master@{#35855}
-
balazs.kilvady authored
TEST=mjsunit/asm/embenchen/zlib BUG= Review-Url: https://codereview.chromium.org/1925543003 Cr-Commit-Position: refs/heads/master@{#35854}
-
jochen authored
R=ulan@chromium.org BUG= Review-Url: https://codereview.chromium.org/1918403003 Cr-Commit-Position: refs/heads/master@{#35853}
-
verwaest authored
Flat cons-strings point directly to the internalized version of the string. This makes reinternalization much faster. BUG= Review-Url: https://codereview.chromium.org/1932663002 Cr-Commit-Position: refs/heads/master@{#35852}
-
epertoso authored
Revert of [ignition] Inline the binary op TurboFan code stubs in the bytecode handlers. (patchset #4 id:60001 of https://codereview.chromium.org/1902823002/ ) Reason for revert: Caused a performance regression in TurboFan and did not improve in a significant way Ignition's performances. Original issue's description: > [ignition] Inline the binary op TurboFan code stubs in the bytecode handlers. > > Adds a Generate method to the stubs that can be used to embed the graph directly in the bytecode handlers. > > Committed: https://crrev.com/e8caf78ff2a9f7d50ac9b47f6b4c80f92b69914a > Cr-Commit-Position: refs/heads/master@{#35696} TBR=bmeurer@chromium.org,rmcilroy@chromium.org,machenbach@chromium.org # Not skipping CQ checks because original CL landed more than 1 days ago. Review-Url: https://codereview.chromium.org/1927873002 Cr-Commit-Position: refs/heads/master@{#35851}
-
neis authored
This fixes a bug where the iterable's .return method gets called when it shouldn't. R=littledan@chromium.org BUG=v8:4952 LOG=n Review-Url: https://codereview.chromium.org/1927073002 Cr-Commit-Position: refs/heads/master@{#35850}
-
yangguo authored
NOTRY=true TBR=machenbach@chromium.org BUG=v8:4961 LOG=N Review-Url: https://codereview.chromium.org/1928893002 Cr-Commit-Position: refs/heads/master@{#35849}
-
mstarzinger authored
This is a preparatory change to only use the class in question when allocating a CompilationInfo on the C-heap for a compilation job. As a next step we will make CompilationInfoWithZone disappear and make the CompilationJob be the one C-heap allocated object. R=bmeurer@chromium.org Review-Url: https://codereview.chromium.org/1931573003 Cr-Commit-Position: refs/heads/master@{#35848}
-
jacob.bramley authored
Remove a couple of variables that are written but not read. BUG= Review-Url: https://codereview.chromium.org/1923913002 Cr-Commit-Position: refs/heads/master@{#35847}
-
verwaest authored
BUG=v8:4932 LOG=n Review-Url: https://codereview.chromium.org/1929853002 Cr-Commit-Position: refs/heads/master@{#35846}
-
yangguo authored
TBR=machenbach@chromium.org BUG=v8:4961 LOG=N NOTRY=true Review-Url: https://codereview.chromium.org/1924093004 Cr-Commit-Position: refs/heads/master@{#35845}
-
mlippautz authored
BUG=chromium:607226, chromium:581412 LOG=N Review-Url: https://codereview.chromium.org/1928883002 Cr-Commit-Position: refs/heads/master@{#35844}
-
clemensh authored
It's more readable than the construction Vector<T>(buffer, arraysize(buffer)). All those places are now replaced by ArrayVector(buffer). R=titzer@chromium.org, jarin@chromium.org, rossberg@chromium.org Review-Url: https://codereview.chromium.org/1916393002 Cr-Commit-Position: refs/heads/master@{#35843}
-
yangguo authored
R=machenbach@chromium.org BUG=v8:4961 NOTRY=true LOG=N NOTREECHECKS=true Review-Url: https://codereview.chromium.org/1915033008 Cr-Commit-Position: refs/heads/master@{#35842}
-
lpy authored
Currently we already have tools to extract C++ symbols of d8, and output the statistics result. This patch creates two scripts, one is to use exsisting tools to extract C++ symbols and dump to output, the other collects all symbols and merges them into v8 log. The format of C++ symbols in v8 log is: cpp,start_address,size,symbol_name BUG=v8:4906 LOG=n Review-Url: https://codereview.chromium.org/1884493003 Cr-Commit-Position: refs/heads/master@{#35841}
-
yangguo authored
R=mstarzinger@chromium.org BUG=v8:4690 LOG=N Review-Url: https://codereview.chromium.org/1921853005 Cr-Commit-Position: refs/heads/master@{#35840}
-
v8-autoroll authored
Rolling v8/buildtools to cdbd50759bf2289d2c9d3f1f7d02239b4b4b1209 Rolling v8/tools/clang to 4652e9c8cea11f68101411f5826eca51b4838eda Rolling v8/tools/gyp to e24c83726b7294179f479a683eeb351568fcc4ee TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/1926883003 Cr-Commit-Position: refs/heads/master@{#35839}
-
- 27 Apr, 2016 5 commits
-
-
bjaideep authored
Port 306c412c Original commit message: This is needed by Blink to implement the Custom Elements spec. R=adamk@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com BUG=v8:4261 LOG=N Review-Url: https://codereview.chromium.org/1929703002 Cr-Commit-Position: refs/heads/master@{#35838}
-
caitpotter88 authored
Return the empty string from StringPad if the filler argument is the empty string, effectively returning the string unchanged in StringPadStart and StringPadEnd. ``` "foo".padStart(100000, "") -> "foo" ``` BUG=v8:4957, v8:4954 LOG=N R=littledan@chromium.org Review-Url: https://codereview.chromium.org/1926773003 Cr-Commit-Position: refs/heads/master@{#35837}
-
caitpotter88 authored
BUG=v8:4954 LOG=Y R=littledan@chromium.org Review-Url: https://codereview.chromium.org/1932453002 Cr-Commit-Position: refs/heads/master@{#35836}
-
littledan authored
The legacy function declaration locations from Annex B 3.2 and 3.4 do not apply for generator declarations. This patch cracks down on those usages, which is tested for by new incoming test262 tests. BUG=v8:4824 LOG=Y R=adamk Review-Url: https://codereview.chromium.org/1900033003 Cr-Commit-Position: refs/heads/master@{#35835}
-
mstarzinger authored
The status FAILED and BAILED_OUT only distinguishes between whether an exception is pending or not. Such a distinction is obsolete by now as all callers check for pending exceptions directly. Also it is impossible for any concurrent part of the job to actually set a pending exception, hence even the assertion that the concurrent part does not return FAILED is obsolete. R=bmeurer@chromium.org Review-Url: https://codereview.chromium.org/1926693003 Cr-Commit-Position: refs/heads/master@{#35834}
-