- 11 Mar, 2015 11 commits
-
-
svenpanne authored
Combined the various lists, the only slightly ugly thing is now the distinction between intrinsics returning pairs and the rest, but that's no big deal. BUG=v8:3947 LOG=n Review URL: https://codereview.chromium.org/989273003 Cr-Commit-Position: refs/heads/master@{#27135}
-
loislo authored
I did some investigation and found that in the most cases the old schema with the separate List for functions and inlines gives us no memory benefits because more frequently we inlines different functions into parent function. So the plain schema wins a tens or even hundreds bytes a few thousand times. The only drawback is that we will print the inlined body the each time when we inline it. But is not a problem because it happens only under FLAG_hydrogen_track_positions. Also I added script_id to the structure, so it could be used later by cpu-profiler. BUG=chromium:452067 LOG=n Review URL: https://codereview.chromium.org/996153003 Cr-Commit-Position: refs/heads/master@{#27134}
-
balazs.kilvady authored
Port a925f3f4 Original commit message: The same idea as in https://codereview.chromium.org/984893003/ BUG=chromium:452067 LOG=n Review URL: https://codereview.chromium.org/996883002 Cr-Commit-Position: refs/heads/master@{#27133}
-
mstarzinger authored
The external v8::TryCatch handler was computed eagerly and kept in intact. This changes it to be computed lazily for simplicity and readability of the code. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/997863003 Cr-Commit-Position: refs/heads/master@{#27132}
-
svenpanne authored
This recovers the performance loss for some ancient benchmarks. Added some comments/UNIMPLEMENTED on the way. BUG=v8:3947 LOG=n Review URL: https://codereview.chromium.org/996153002 Cr-Commit-Position: refs/heads/master@{#27131}
-
dcarney authored
BUG=v8:3929 LOG=n Review URL: https://codereview.chromium.org/998943002 Cr-Commit-Position: refs/heads/master@{#27130}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/998893002 Cr-Commit-Position: refs/heads/master@{#27129}
-
hpayer authored
Just visit young array buffers during scavenge. Additionally keep the views in new space in a separate global list and move them to the corresponding array buffers when they get promoted. BUG= Review URL: https://codereview.chromium.org/990423004 Cr-Commit-Position: refs/heads/master@{#27128}
-
mstarzinger authored
This removes the separate tracking of the pending message script, because that script is already stored in the message object and duplicating it in the ThreadLocalTop makes it more brittle. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/995013005 Cr-Commit-Position: refs/heads/master@{#27127}
-
dcarney authored
BUG= Review URL: https://codereview.chromium.org/993223003 Cr-Commit-Position: refs/heads/master@{#27126}
-
michael_dawson authored
Contribution of PowerPC port (continuation of 422063005, 817143002,866843003, and 901083004). This patch updates the ppc directories to make them current with changes in common code as of today. We had to exclude the test test-serialize/SerializeInternalReference until we agree on the right way to add those changes for PPC as outlined in the description in the google doc provided earlier. We also had to exclude a couple of other tests due to new failures seen since the last uplevel. We excluded as opposed to waiting until we could investigate to maximize the chance of getting PPC compiling in the google repos before new breaking changes are made. I'll note that before applying any of our changes the mozilla part of quickcheck was already broken when using the lastest repo content so I had to run without that modified: src/compiler/ppc/code-generator-ppc.cc modified: src/compiler/ppc/instruction-codes-ppc.h modified: src/compiler/ppc/instruction-selector-ppc.cc modified: src/ic/ppc/handler-compiler-ppc.cc modified: src/ic/ppc/ic-compiler-ppc.cc modified: src/ppc/assembler-ppc-inl.h modified: src/ppc/assembler-ppc.cc modified: src/ppc/assembler-ppc.h modified: src/ppc/builtins-ppc.cc modified: src/ppc/code-stubs-ppc.cc modified: src/ppc/codegen-ppc.cc modified: src/ppc/full-codegen-ppc.cc modified: src/ppc/lithium-codegen-ppc.cc modified: src/ppc/macro-assembler-ppc.cc modified: src/ppc/macro-assembler-ppc.h modified: test/cctest/cctest.status R=danno@chromium.org, svenpanne@chromium.org BUG= Review URL: https://codereview.chromium.org/994533004 Cr-Commit-Position: refs/heads/master@{#27125}
-
- 10 Mar, 2015 29 commits
-
-
bashi authored
We should be able to cast a Value to Boolean when IsBoolean() is true. Review URL: https://codereview.chromium.org/990943003 Cr-Commit-Position: refs/heads/master@{#27124}
-
paul.lind authored
Port 36e69a91 Original commit message: This reduces the size of the StackHandler by yet another word. We no longer need to keep track of the frame pointer, as the stack walk will be able to recalculate it. BUG= Review URL: https://codereview.chromium.org/997663002 Cr-Commit-Position: refs/heads/master@{#27123}
-
caitpotter88 authored
BUG=v8:3954 LOG=N R=arv@chromium.org Review URL: https://codereview.chromium.org/987203003 Cr-Commit-Position: refs/heads/master@{#27122}
-
dcarney authored
the implementation doesn't yet throw on strict mode assignment BUG= Review URL: https://codereview.chromium.org/992913002 Cr-Commit-Position: refs/heads/master@{#27121}
-
balazs.kilvady authored
Port e0aa8ebf Original commit message: This reduces the size of the StackHandler by one word. We no longer need to keep track of the code object, as the stack walk finds it. BUG= Review URL: https://codereview.chromium.org/990903008 Cr-Commit-Position: refs/heads/master@{#27120}
-
balazs.kilvady authored
Port 8d946b9c Original commit message: The prototype of a class constructor function is read only. When we set computed property names we were ignoring this and we were overriding the property. Since the prototype is the only possible own read only property on the constructor function object we special case this so we do not have to check this for every property in the class literal. BUG=v8:3945 LOG=N Review URL: https://codereview.chromium.org/993963003 Cr-Commit-Position: refs/heads/master@{#27119}
-
marja authored
This CL adds errors for illegal references which occur inside object literal methods inside computed properrty names. BUG=v8:3948,v8:3956 LOG=N Review URL: https://codereview.chromium.org/994043003 Cr-Commit-Position: refs/heads/master@{#27118}
-
balazs.kilvady authored
Port 022ea7e0 Original commit message: Provide an intrinsic %MathFloor / %_MathFloor that is used to optimize both Math.ceil and Math.floor, and use the JS inlining mechanism to inline Math.ceil into TurboFan code. Although we need to touch code outside of TurboFan to make this work, this does not affect the way we handle Math.ceil and/or Math.floor in CrankShaft, because for CrankShaft the old-style builtin function id based inlining still kicks in first. Once this solution is stabilized, we can use it for Math.floor as well. And once that is settled, we can establish it as the unified way to inline builtins, and get rid of the specialized builtin function id based inlining at some point. Note that "builtin" applies to basically every piece of internal JavaScript/intrinsics based code, so this also applies to the yet to be defined JavaScript based code stubs and handlers. BUG=v8:3953 LOG=n Review URL: https://codereview.chromium.org/998503002 Cr-Commit-Position: refs/heads/master@{#27117}
-
loislo authored
Four tests are failing due to a problem with no frame ranges. BUG= LOG=n Committed: https://crrev.com/2be160e726f2be6272b77e53fbd556aded6024f1 Cr-Commit-Position: refs/heads/master@{#27035} Review URL: https://codereview.chromium.org/976203003 Cr-Commit-Position: refs/heads/master@{#27116}
-
mstarzinger authored
This reduces the size of the StackHandler by yet another word. We no longer need to keep track of the frame pointer, as the stack walk will be able to recalculate it. R=yangguo@chromium.org Review URL: https://codereview.chromium.org/991893003 Cr-Commit-Position: refs/heads/master@{#27115}
-
loislo authored
The same idea as in https://codereview.chromium.org/984893003/ BUG=chromium:452067 LOG=n Review URL: https://codereview.chromium.org/997513003 Cr-Commit-Position: refs/heads/master@{#27114}
-
yurys authored
None of these fields is used in Blink. Embedder always can implement them using existing API. BUG=chromium:465651 LOG=Y Review URL: https://codereview.chromium.org/983833006 Cr-Commit-Position: refs/heads/master@{#27113}
-
loislo authored
BUG=chromium:452067 LOG=n R=svenpanne@chromium.org, jacob.bramley@arm.com, yurys@chromium.org Review URL: https://codereview.chromium.org/995813002 Cr-Commit-Position: refs/heads/master@{#27112}
-
Ben L. Titzer authored
R=verwaest@chromium.org BUG= Review URL: https://codereview.chromium.org/979323005 Cr-Commit-Position: refs/heads/master@{#27111}
-
svenpanne authored
Doing a runtime call should always be better than totally giving up (unless we have fullcode-only intrinsics, which we'll probably never have). BUG=v8:3947 LOG=n Review URL: https://codereview.chromium.org/997543002 Cr-Commit-Position: refs/heads/master@{#27110}
-
mstarzinger authored
This makes sure that the pending message location is only tracked by the message object, as only this is saved for finally-blocks. The location information is duplicated and becomes stale. R=titzer@chromium.org TEST=maeh, not so much. Review URL: https://codereview.chromium.org/987353002 Cr-Commit-Position: refs/heads/master@{#27109}
-
jarin authored
BUG=chromium:465701 LOG=n R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/993773004 Cr-Commit-Position: refs/heads/master@{#27108}
-
hpayer authored
There are no stale store buffer pointers anymore. The sweeper thread can not be in conflict with store buffer processing. BUG= Review URL: https://codereview.chromium.org/993983002 Cr-Commit-Position: refs/heads/master@{#27107}
-
arv authored
The prototype of a class constructor function is read only. When we set computed property names we were ignoring this and we were overriding the property. Since the prototype is the only possible own read only property on the constructor function object we special case this so we do not have to check this for every property in the class literal. BUG=v8:3945 LOG=N R=mstarzinger@chromium.org, dslomov@chromium.org Review URL: https://codereview.chromium.org/985643003 Cr-Commit-Position: refs/heads/master@{#27106}
-
hpayer authored
We can do that now since we have the invariant that the store buffer always has valid slots after marking. BUG= Review URL: https://codereview.chromium.org/991853002 Cr-Commit-Position: refs/heads/master@{#27105}
-
hpayer authored
BUG= Review URL: https://codereview.chromium.org/978983003 Cr-Commit-Position: refs/heads/master@{#27104}
-
mstarzinger authored
This reduces the size of the StackHandler by one word. We no longer need to keep track of the code object, as the stack walk finds it. R=yangguo@chromium.org Review URL: https://codereview.chromium.org/985803002 Cr-Commit-Position: refs/heads/master@{#27103}
-
svenpanne authored
We can remove a few of them now (those which unconditionally bailout), but this will be done in a separate CL to see any impact separately. BUG=v8:3947 LOG=n Review URL: https://codereview.chromium.org/993963002 Cr-Commit-Position: refs/heads/master@{#27102}
-
v8-autoroll authored
Rolling v8/tools/clang to ed79fd57317ab9f09ce52a5e1c7424eebb80a73e BUG=chromium:464657 LOG=n TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/988623002 Cr-Commit-Position: refs/heads/master@{#27101}
-
Sven Panne authored
Note that this patch is not really a *solution*, it is just enough to make the undefined behavior unobservable. The real fix would be being much more correct about sizes and signedness in our code base... BUG=chromium:464657 LOG=n R=dcarney@chromium.org Review URL: https://codereview.chromium.org/995743002 Cr-Commit-Position: refs/heads/master@{#27100}
-
jarin authored
BUG=chromium:465645 LOG=n R=titzer@chromium.org Review URL: https://codereview.chromium.org/996663002 Cr-Commit-Position: refs/heads/master@{#27099}
-
bmeurer authored
BUG=v8:3952 LOG=n R=yangguo@chromium.org Review URL: https://codereview.chromium.org/997513002 Cr-Commit-Position: refs/heads/master@{#27098}
-
yurys authored
BUG=None LOG=Y Review URL: https://codereview.chromium.org/992193002 Cr-Commit-Position: refs/heads/master@{#27097}
-
marja authored
The bits in CompilerHints are accessed via FunctionKindBits, and on the other hand, with accessors defined by BOOL_ACCESSORS(SharedFunctionInfo, compiler_hints, is_accessor_function, kIsAccessorFunction) etc. So the bit order in FunctionKind must match CompilerHints. This is not causing problems (yet) because there's no accessor for these two bits, but if somebody adds one, things will go wrong. R=dslomov@chromium.org BUG= Review URL: https://codereview.chromium.org/988413002 Cr-Commit-Position: refs/heads/master@{#27096}
-