- 20 Nov, 2013 23 commits
-
-
mvstanton@chromium.org authored
The problem was that we don't use crankshaft on non-sse2 builds. (on ARM non-vfp3). R=danno@chromium.org Review URL: https://codereview.chromium.org/77963002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17930 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mvstanton@chromium.org authored
A problem arises in recursive literal expressions due to recent changes that defer allocation of constant literal properties from parse time. We were calculating expression depth as a side-effect of a lazy constant property build, but subsequent calls for the depth always returned 1. Cache the correct depth in the MaterializedLiteral instead. (Related-to/very-partial-revert-of https://codereview.chromium.org/61873003) R=ulan@chromium.org Review URL: https://codereview.chromium.org/78493002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17929 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/77853003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17926 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
R=ulan@chromium.org Review URL: https://codereview.chromium.org/60763006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17925 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
m.m.capewell@googlemail.com authored
Optimize register constraints and code generated for AccessArgumentsAt Lithium instruction. TEST=none BUG= R=ulan@chromium.org Review URL: https://codereview.chromium.org/78093004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17923 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
verwaest@chromium.org authored
R=dslomov@chromium.org Review URL: https://chromiumcodereview.appspot.com/76403002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17922 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
danno@chromium.org authored
R=ulan@chromium.org Review URL: https://chromiumcodereview.appspot.com/59813011 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17921 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
Generate a proper subgraph in BuildBinaryOperation instead. R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/77053003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17919 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
It results in a lot of dead code, and Isolate::PrintStack itself crashes most of the time when something went wrong earlier. Furthermore, we have plans do get better information into the minidump, anyway. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/78003002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17918 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
TEST=mjsunit/number-tostring R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/77553005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17917 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
> This will allow for using gin and blink bindings in the same process > > BUG=317398 > R=svenpanne@chromium.org, dcarney@chromium.org > LOG=y > > Review URL: https://codereview.chromium.org/77913003 BUG=none R=svenpanne@chromium.org TBR=svenpanne@chromium.org LOG=n Review URL: https://codereview.chromium.org/78093005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17915 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/78183002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17914 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/78213002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17913 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
If we know that one side of a string add is definitely a string (i.e. if it's a string constant), then we don't need to emit a string check for the argument. This adds a new BuildCheckString() method to the graph builder, which does "the right thing". TEST=mjsunit/string-add R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/78063002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17912 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
LOG=Y R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/62193003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17910 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
BUG=312241 LOG=Y R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/59823008 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17909 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
This will allow for using gin and blink bindings in the same process BUG=317398 R=svenpanne@chromium.org, dcarney@chromium.org LOG=y Review URL: https://codereview.chromium.org/77913003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17907 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dcarney@chromium.org authored
this is implemented for intel platforms only, as they are the only ones which show speed up with this change R=svenpanne@chromium.org BUG= Review URL: https://codereview.chromium.org/48303002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17903 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
bmeurer@chromium.org authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/77943002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17899 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
R=danno@chromium.org BUG= Review URL: https://codereview.chromium.org/77673004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17896 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mvstanton@chromium.org authored
it's failure is diagnosed. R=danno@chromium.org Review URL: https://codereview.chromium.org/77923002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17894 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
This CL depends on https://codereview.chromium.org/65933003/. BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/67763005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17893 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/65933003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17892 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 19 Nov, 2013 17 commits
-
-
plind44@gmail.com authored
Port r17886 (e2fb3ed) Original commit message: The %_OneByteSeqStringSetChar intrinsic expects its arguments to be checked before being called for efficiency reasons, but the fuzzer provided no such checks. Now the intrinsic is robust to bad input if FLAG_debug_code is set. R=plind44@gmail.com, yangguo@chromium.org TEST=test/mjsunit/regress/regress-320948.js BUG=chromium:320948 LOG=Y Review URL: https://codereview.chromium.org/68793008 Patch from Balazs Kilvady <kilvadyb@homejinni.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17891 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
danno@chromium.org authored
This fixes unused variable compile failures in release builds introduced in r17887. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/76413004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17888 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mvstanton@chromium.org authored
Verify that code objects are treated weakly by the AllocationSite dependent_code field. R=ulan@chromium.org Review URL: https://codereview.chromium.org/61923006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17887 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
danno@chromium.org authored
The %_OneByteSeqStringSetChar intrinsic expects its arguments to be checked before being called for efficiency reasons, but the fuzzer provided no such checks. Now the intrinsic is robust to bad input if FLAG_debug_code is set. R=yangguo@chromium.org TEST=test/mjsunit/regress/regress-320948.js BUG=chromium:320948 LOG=Y Review URL: https://codereview.chromium.org/72813004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17886 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
plind44@gmail.com authored
Port r17867 (a305bd3) BUG= R=plind44@gmail.com Review URL: https://codereview.chromium.org/60763005 Patch from Balazs Kilvady <kilvadyb@homejinni.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17885 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
plind44@gmail.com authored
Port r17865 (5b2e594) BUG= R=plind44@gmail.com Review URL: https://codereview.chromium.org/76163003 Patch from Balazs Kilvady <kilvadyb@homejinni.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17884 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
This also reverts 17879 and 17880. BUG=v8:3015 TBR=svenpanne@chromium.org LOG=n Review URL: https://codereview.chromium.org/76323002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17881 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
TBR=svenpanne@chromium.org BUG=none LOG=n Review URL: https://codereview.chromium.org/67463003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17880 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
TBR=svenpanne@chromium.org BUG=none LOG=n Review URL: https://codereview.chromium.org/76313002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17879 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
This broke after a recent refactoring. BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/76193002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17878 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
Also provide a default implementation to use in cctests. For now, there are just two thread releated callbacks. In future CLs, I will move callbacks registered e.g. via V8::SetFooCallback over. BUG=v8:3015 R=svenpanne@chromium.org, danno@chromium.org LOG=no Review URL: https://codereview.chromium.org/75283002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17877 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
verwaest@chromium.org authored
BUG= R=dcarney@chromium.org Review URL: https://chromiumcodereview.appspot.com/67613005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17876 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=svenpanne@chromium.org BUG= Review URL: https://codereview.chromium.org/76293003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17875 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
BUG=321060 LOG=n R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/73463004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17874 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
This is currently not observable without --allow-natives-syntax because all internal usages are safe, but it deserves to be fixed nonetheless. BUG=chromium:320922 LOG=N R=yangguo@chromium.org Review URL: https://codereview.chromium.org/67103003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17873 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
R=bmeurer@chromium.org, machenbach@chromium.org, svenpanne@chromium.org LOG=y BUG=none Review URL: https://codereview.chromium.org/63093004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17869 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=svenpanne@chromium.org BUG= Review URL: https://codereview.chromium.org/61163007 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17868 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-