- 12 Apr, 2016 7 commits
-
-
gdeepti authored
Add relocatable pointers for wasm memory references that need to be updated when wasm GrowMemory is used. Code generator changes to accept relocatable constants as immediates. R=titzer@chromium.org, yangguo@chromium.org, bradnelson@chromium.org Committed: https://crrev.com/eb5fe0df64ec0add423b2a1f6fb62d5a33dce2a5 Cr-Commit-Position: refs/heads/master@{#35182} Committed: https://crrev.com/297932a302ce0b73c3618ef9e4eba9d9d241f2b3 Cr-Commit-Position: refs/heads/master@{#35400} Review URL: https://codereview.chromium.org/1759383003 Cr-Commit-Position: refs/heads/master@{#35407}
-
oth authored
Fixes updating golden files following instanceof change. BUG=v8:4280 LOG=N R=rmcilroy@chromium.org,ssanfilippo@chromium.org Review URL: https://codereview.chromium.org/1858593002 Cr-Commit-Position: refs/heads/master@{#35406}
-
mbrandy authored
Port 79ff6507 R=verwaest@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, bjaideep@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1874983004 Cr-Commit-Position: refs/heads/master@{#35405}
-
hablich authored
Revert of Visit the Optimized Code Map on first call rather than closure creation. (patchset #7 id:120001 of https://codereview.chromium.org/1670143002/ ) Reason for revert: Blocks roll. See https://codereview.chromium.org/1877003002/ for detailed messages. You should be able to repro this with Linux ASAN. Original issue's description: > Visit the Optimized Code Map on first call rather than closure creation. > > This is useful for escape analysis, and helps upcoming changes to > type feedback gathering. > > BUG= > > Committed: https://crrev.com/9336f4cc6d25d39a128176679a70dbd13a6d946e > Cr-Commit-Position: refs/heads/master@{#35395} TBR=mstarzinger@chromium.org,bmeurer@chromium.org,mvstanton@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/1878063004 Cr-Commit-Position: refs/heads/master@{#35404}
-
ahaas authored
The parameter is not used at the moment, so I removed it. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1876833003 Cr-Commit-Position: refs/heads/master@{#35403}
-
bmeurer authored
Make these builtins fast by default w/o relying on the %_StringCharCodeAt and %_StringCharAt intrinsics, which we cannot deal with well in TurboFan (and ignition). CQ_INCLUDE_TRYBOTS=tryserver.v8:v8_linux_nosnap_dbg R=epertoso@chromium.org Committed: https://crrev.com/43d3331d87f68ea7efa1b58f559f33f60e5dacfb Cr-Commit-Position: refs/heads/master@{#35350} Review URL: https://codereview.chromium.org/1868963002 Cr-Commit-Position: refs/heads/master@{#35402}
-
machenbach authored
Revert of [compiler] Add relocatable pointer constants for wasm memory references. (patchset #15 id:320001 of https://codereview.chromium.org/1759383003/ ) Reason for revert: [Sheriff] Breaks msan: https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20MSAN/builds/7842 Original issue's description: > [compiler] Add relocatable pointer constants for wasm memory references. > > Add relocatable pointers for wasm memory references that need to be updated when wasm GrowMemory is used. Code generator changes to accept relocatable constants as immediates. > > R=titzer@chromium.org, yangguo@chromium.org, bradnelson@chromium.org > > Committed: https://crrev.com/eb5fe0df64ec0add423b2a1f6fb62d5a33dce2a5 > Cr-Commit-Position: refs/heads/master@{#35182} > > Committed: https://crrev.com/297932a302ce0b73c3618ef9e4eba9d9d241f2b3 > Cr-Commit-Position: refs/heads/master@{#35400} TBR=bradnelson@chromium.org,titzer@chromium.org,bmeurer@chromium.org,bradnelson@google.com,gdeepti@google.com # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/1881913002 Cr-Commit-Position: refs/heads/master@{#35401}
-
- 11 Apr, 2016 32 commits
-
-
gdeepti authored
Add relocatable pointers for wasm memory references that need to be updated when wasm GrowMemory is used. Code generator changes to accept relocatable constants as immediates. R=titzer@chromium.org, yangguo@chromium.org, bradnelson@chromium.org Committed: https://crrev.com/eb5fe0df64ec0add423b2a1f6fb62d5a33dce2a5 Cr-Commit-Position: refs/heads/master@{#35182} Review URL: https://codereview.chromium.org/1759383003 Cr-Commit-Position: refs/heads/master@{#35400}
-
jarin authored
Review URL: https://codereview.chromium.org/1856643002 Cr-Commit-Position: refs/heads/master@{#35399}
-
hablich authored
Reland of [compiler] Make feedback vector cope with flag changes. (patchset #1 id:1 of https://codereview.chromium.org/1876103002/ ) Reason for revert: Did not fail on another roll including this CL .. Original issue's description: > Revert of [compiler] Make feedback vector cope with flag changes. (patchset #1 id:1 of https://codereview.chromium.org/1869693003/ ) > > Reason for revert: > Blocks current roll: https://codereview.chromium.org/1876713002/ according to bisect: https://codereview.chromium.org/1872353002/#ps80001 > > Original issue's description: > > [compiler] Make feedback vector cope with flag changes. > > > > This fixes corner cases where the layout of feedback vectors baked into > > the snapshot is different from the expected layout, depending on some > > runtime flags. We make sure the feedback vector is regenereated for > > functions that are not compiled. Flag changes of this kind are only > > allowed when code is not serialized. > > > > An alternative solution would be to not serialize the feedback vector > > for such cases in the first place. That solution however would have a > > higher overhead, as it would required the serializer to be able to > > recognize feedback vectors while generating a snapshot. > > > > R=mvstanton@chromium.org > > TEST=mjsunit/regress/regress-crbug-600995 > > BUG=chromium:600995 > > LOG=n > > > > Committed: https://crrev.com/460bff5fb6af2bd79e610f89afdf6da9dba3cf0c > > Cr-Commit-Position: refs/heads/master@{#35339} > > TBR=mvstanton@chromium.org,mstarzinger@chromium.org > > BUG=chromium:600995 > LOG=N > NOTRY=true > > Committed: https://crrev.com/78049e9c4837f053575d6c71e53ae12fec99f1aa > Cr-Commit-Position: refs/heads/master@{#35392} TBR=mvstanton@chromium.org,mstarzinger@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:600995 Review URL: https://codereview.chromium.org/1876973002 Cr-Commit-Position: refs/heads/master@{#35398}
-
jkummerow authored
This logic mirrors what KeyedLoadICs are doing already. BUG=chromium:602184 LOG=n Review URL: https://codereview.chromium.org/1876793003 Cr-Commit-Position: refs/heads/master@{#35397}
-
https://codereview.chromium.org/1877453002/machenbach authored
Reason for revert: Breaks gc mole: https://build.chromium.org/p/client.v8/builders/V8%20Linux/builds/9421 Original issue's description: > Fix printf formats > > The usage of __attribute__((format(x, y)) was either wrong or missing from multiple functions, leading to erroneous formats. This CL: > > - Imports PRINTF_FORMAT macro from Chrome's src/base/compiler-specific.h. > - Uses it appropriately. > - Imports Chrome's base/format_macros.h mainly to fix size_t formats (further cleanup could be done). > - Fixes a bunch of incorrect formats. > > Original CL: https://codereview.chromium.org/1869433004 > Reverted in: https://codereview.chromium.org/1867383002 > > R= jochen@chromium.org > TBR= bmeurer@chromium.org, yangguo@chromium.org, ahaas@chromium.org > > Committed: https://crrev.com/bf505329288e1b75bab0e6800371a9aac40fa5cc > Cr-Commit-Position: refs/heads/master@{#35394} TBR=jochen@chromium.org,ahaas@chromium.org,bmeurer@chromium.org,yangguo@chromium.org,jfb@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/1877823003 Cr-Commit-Position: refs/heads/master@{#35396}
-
mvstanton authored
This is useful for escape analysis, and helps upcoming changes to type feedback gathering. BUG= Review URL: https://codereview.chromium.org/1670143002 Cr-Commit-Position: refs/heads/master@{#35395}
-
jfb authored
The usage of __attribute__((format(x, y)) was either wrong or missing from multiple functions, leading to erroneous formats. This CL: - Imports PRINTF_FORMAT macro from Chrome's src/base/compiler-specific.h. - Uses it appropriately. - Imports Chrome's base/format_macros.h mainly to fix size_t formats (further cleanup could be done). - Fixes a bunch of incorrect formats. Original CL: https://codereview.chromium.org/1869433004 Reverted in: https://codereview.chromium.org/1867383002 R= jochen@chromium.org TBR= bmeurer@chromium.org, yangguo@chromium.org, ahaas@chromium.org Review URL: https://codereview.chromium.org/1877453002 Cr-Commit-Position: refs/heads/master@{#35394}
-
verwaest authored
Otherwise they can't be found in the megamorphic cache, leading to repeated misses. BUG=chromium:596825 LOG=n Review URL: https://codereview.chromium.org/1874303002 Cr-Commit-Position: refs/heads/master@{#35393}
-
hablich authored
Revert of [compiler] Make feedback vector cope with flag changes. (patchset #1 id:1 of https://codereview.chromium.org/1869693003/ ) Reason for revert: Blocks current roll: https://codereview.chromium.org/1876713002/ according to bisect: https://codereview.chromium.org/1872353002/#ps80001 Original issue's description: > [compiler] Make feedback vector cope with flag changes. > > This fixes corner cases where the layout of feedback vectors baked into > the snapshot is different from the expected layout, depending on some > runtime flags. We make sure the feedback vector is regenereated for > functions that are not compiled. Flag changes of this kind are only > allowed when code is not serialized. > > An alternative solution would be to not serialize the feedback vector > for such cases in the first place. That solution however would have a > higher overhead, as it would required the serializer to be able to > recognize feedback vectors while generating a snapshot. > > R=mvstanton@chromium.org > TEST=mjsunit/regress/regress-crbug-600995 > BUG=chromium:600995 > LOG=n > > Committed: https://crrev.com/460bff5fb6af2bd79e610f89afdf6da9dba3cf0c > Cr-Commit-Position: refs/heads/master@{#35339} TBR=mvstanton@chromium.org,mstarzinger@chromium.org BUG=chromium:600995 LOG=N NOTRY=true Review URL: https://codereview.chromium.org/1876103002 Cr-Commit-Position: refs/heads/master@{#35392}
-
mstarzinger authored
This moves the computation of the {expected_nof_properties} for a shared function to where the object is actually being allocated. This is done after parsing when the literal has been populated already. The expected number of properties is not mutated after parsing. R=verwaest@chromium.org Review URL: https://codereview.chromium.org/1873173002 Cr-Commit-Position: refs/heads/master@{#35391}
-
machenbach authored
BUG=535160 TBR=sergiyb@chromium.org, kjellander@chromium.org NOTRY=true NOPRESUBMIT=true Review URL: https://codereview.chromium.org/1872423002 Cr-Commit-Position: refs/heads/master@{#35390}
-
epertoso authored
Adds a ModulusStub for the modulo operator and lets TurboFan and Ignition make use of it. Review URL: https://codereview.chromium.org/1876793002 Cr-Commit-Position: refs/heads/master@{#35389}
-
mstarzinger authored
This makes sure that --hydrogen-filter only filters for Crankshaft, not for TurboFan compilations. For TurboFan there is --turbo-filter as a separate flag already. There no longer is a single flag to filter both compilers at the same time, one can still specify both flags however. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/1871343003 Cr-Commit-Position: refs/heads/master@{#35388}
-
bmeurer authored
We had exactly one test case for --noturbo-types, so it's likely that the generic pipeline (without types) was already broken for quite some time, plus no one expressed interest in maintaining it, plus it complicates the JSGenericLowering integration. So decision is to kill it. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1872333002 Cr-Commit-Position: refs/heads/master@{#35387}
-
verwaest authored
BUG= Committed: https://crrev.com/8764f87a3399ba433a4ce6f32161181c713af95c Cr-Commit-Position: refs/heads/master@{#35376} Review URL: https://codereview.chromium.org/1864703003 Cr-Commit-Position: refs/heads/master@{#35386}
-
ishell authored
[deoptimizer] Extend assert to also expect kTailCallerFunction as bottommost frame when accessing arguments for inlined function. BUG=chromium:601617, v8:4698 LOG=N Review URL: https://codereview.chromium.org/1876753002 Cr-Commit-Position: refs/heads/master@{#35385}
-
mstarzinger authored
R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1872833002 Cr-Commit-Position: refs/heads/master@{#35384}
-
mythria authored
Function bindings are the only variables in LEGACY_CONST mode. (https://codereview.chromium.org/1819123002/). Since these variables can also be accessed in strict mode functions we should support handling such variables. Assigning to a legacy constant throws a TypeError in strict mode. Also fixes hydrogen.cc to throw a TypeError for legacy constants. BUG=v8:4280,chromium:599068 LOG=N TBR=rmcilroy@chromium.org Review URL: https://codereview.chromium.org/1845223006 Cr-Commit-Position: refs/heads/master@{#35383}
-
machenbach authored
This removes the "AboutToRun" callback. It makes not much sense as it is not actually called before a test is run, but just before the results are retrieved from the results queue. Therefore, from an information-value p-o-v it is redundant to the "HasRun" callback. This also reduces log size on the bots by 50%, in order to reduce buildbot slowness, which is tied to the amount of logs. Review URL: https://codereview.chromium.org/1874973003 Cr-Commit-Position: refs/heads/master@{#35382}
-
mstarzinger authored
R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1878563002 Cr-Commit-Position: refs/heads/master@{#35381}
-
ssanfilippo authored
When FLAG_trace_ignition_dispatches is enabled, a dispatch counter is kept for each pair of source-destination bytecode handlers. Each counter saturates at max uintptr_t value. Counters are dumped as a JSON-encoded object of objects, such that each key on the top level object is a source bytecode name, and each key on the corresponding value is a destination bytecode name, with the associated counter as value. The output file name can be controlled with the FLAG_trace_ignition_dispatches_output_file flag. The JSON file may be written by calling Interpreter::WriteDispatchCounters(), which is done for d8 in Shell::OnExit, if FLAG_trace_ignition_dispatches is enabled. BUG=v8:4899 LOG=N Review URL: https://codereview.chromium.org/1828633003 Cr-Commit-Position: refs/heads/master@{#35380}
-
machenbach authored
Revert of Turn StoreIC::Megamorphic into a builtin, get rid of the non-monomorphic-cache (patchset #5 id:80001 of https://codereview.chromium.org/1864703003/ ) Reason for revert: [Sheriff] Check during mksnapshot: https://build.chromium.org/p/client.v8/builders/V8%20Linux%20ASAN%20mipsel%20-%20debug%20builder/builds/5950/steps/compile/logs/stdio Original issue's description: > Turn StoreIC::Megamorphic into a builtin, get rid of the non-monomorphic-cache > > BUG= > > Committed: https://crrev.com/8764f87a3399ba433a4ce6f32161181c713af95c > Cr-Commit-Position: refs/heads/master@{#35376} TBR=mvstanton@chromium.org,hpayer@chromium.org,verwaest@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/1875033003 Cr-Commit-Position: refs/heads/master@{#35379}
-
hpayer authored
BUG= Review URL: https://codereview.chromium.org/1878573002 Cr-Commit-Position: refs/heads/master@{#35378}
-
mstarzinger authored
This refactors the OptimizedCompileJob class to be agnostic from the actual underlying compiler. Instead it represents a base class for all compilation jobs. The implementation is provided by the backend by just overriding the phase methods. Also note that this contains the semantics change of not falling back to Crankshaft when TurboFan optimization fails. This fallback is no longer needed and will not be supported going forward. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1872483002 Cr-Commit-Position: refs/heads/master@{#35377}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1864703003 Cr-Commit-Position: refs/heads/master@{#35376}
-
hablich authored
R=machenbach@chromium.org Review URL: https://codereview.chromium.org/1876723002 Cr-Commit-Position: refs/heads/master@{#35375}
-
hpayer authored
Black allocation discards all old-space free-lists, which may be quite full when we perform memory reducing GCs. BUG=chromium:599174 LOG=n Review URL: https://codereview.chromium.org/1869493002 Cr-Commit-Position: refs/heads/master@{#35374}
-
marija.antic authored
Fix for multiple test failures occurring since ResumeGeneratorTrampoline was introduced with the change 974721c6. BUG= Review URL: https://codereview.chromium.org/1869343003 Cr-Commit-Position: refs/heads/master@{#35373}
-
hablich authored
Revert of Use GCC for snapshot_toolchain when is_clang=false. (patchset #1 id:1 of https://codereview.chromium.org/1809643003/ ) Reason for revert: Blocks roll: https://codereview.chromium.org/1874173002/ Original issue's description: > Use GCC for snapshot_toolchain when is_clang=false. > > Currently, snapshot_toolchain is hardcoded to use a clang host > toolchain. Use a GCC toolchain if is_clang is false. > > Revert this when this is root-caused (see crbug.com/601486) > > LOG=Y > BUG=601486 > > Committed: https://crrev.com/920370d1a910681bf464bd91aced316058ea2f6c > Cr-Commit-Position: refs/heads/master@{#35341} TBR=jochen@chromium.org,alokp@chromium.org,dpranke@chromium.org,slan@chromium.org # Not skipping CQ checks because original CL landed more than 1 days ago. BUG=601486 LOG=Y Review URL: https://codereview.chromium.org/1873113002 Cr-Commit-Position: refs/heads/master@{#35372}
-
cbruni authored
BUG= Review URL: https://codereview.chromium.org/1873833002 Cr-Commit-Position: refs/heads/master@{#35371}
-
neis authored
... instead of doing stack magic. This is a cleanup in preparation for the new generators implementation. R=bmeurer@chromium.org BUG= Review URL: https://codereview.chromium.org/1867263002 Cr-Commit-Position: refs/heads/master@{#35370}
-
Ilija.Pavlovic authored
Enabled big endian testing for MIPS32 and MIPS64. The tests are also adapted for big endian variant. TEST=cctest/test-assembler-mips[64] BUG= Review URL: https://codereview.chromium.org/1867503002 Cr-Commit-Position: refs/heads/master@{#35369}
-
- 10 Apr, 2016 1 commit
-
-
bmeurer authored
If we already know that the input to one of the ObjectIs<Type> nodes is TaggedPointer, we don't need to perform the Smi check at runtime. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1872143002 Cr-Commit-Position: refs/heads/master@{#35368}
-