- 18 Jul, 2014 13 commits
-
-
rmcilroy@chromium.org authored
Move android_webview_build variable to toolchain.gypi to fix arm builders. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/398643006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22473 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
hpayer@chromium.org authored
BUG= R=jarin@chromium.org Review URL: https://codereview.chromium.org/397373006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22472 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
hpayer@chromium.org authored
BUG= R=jarin@chromium.org Review URL: https://codereview.chromium.org/398333002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22471 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/392033005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22470 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
The android_webview get's it's compiler flags from the Android build system, so we should not be setting these flags in gyp when building the webview. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/399413002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22467 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
Jacob.Bramley@arm.com authored
The stub cache used kHeapObjectTagSize to scale indices, but there doesn't appear to be a direct need for this. Instead, the stub cache has its own kCacheIndexShift quantity. BUG= R=hpayer@chromium.org Review URL: https://codereview.chromium.org/401613003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22466 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ernstm@chromium.org authored
This is essentially https://codereview.chromium.org/390823003/. It turns out that it's safe to use a persistent GCTracer instead of creating and destroying GCTracers for each GC, because Scavenge and Mark-Sweep steps never overlap, and the tracking of incremental marking also happens separately for the two types of GC. Tracking of incremental marking will be moved into the GCTracer in a follow-up patch. R=hpayer@chromium.org, mstarzinger@chromium.org BUG= Review URL: https://codereview.chromium.org/403543002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22465 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/400913003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22464 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
BUG=381820 LOG=n R=hpayer@chromium.org Review URL: https://codereview.chromium.org/401793002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22463 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
BUG=none LOG=n TBR=danno@chromium.org Review URL: https://codereview.chromium.org/400123002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22462 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
danno@chromium.org authored
R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/397253002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22461 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
dcarney@chromium.org authored
Bootstrapper::DetachGlobal also need to unset global_proxy's constructor to remove all refs to context DetachGlobal detaches original context of a global proxy object. Before this patch, the constructor JSFunction still carried a reference to the old context after |Bootstrapper::DetachGlobal| call. This patch removes the reference by setting the constructor null. TEST=http/tests/security/isolatedWorld w/ --enable-leak-detection LOG=N BUG=364377 R=dcarney@chromium.org Review URL: https://codereview.chromium.org/397953009 Patch from Kouhei Ueno <kouhei@chromium.org>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22460 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
weiliang.lin@intel.com authored
port r22448 original commit message: StubCallInterfaceDescriptor and CallInterfaceDescriptor are unified under a base class InterfaceDescriptor. Handling of the context register had to be massaged to effect the unification. This will make it easier to call hydrogen code stubs directly from crankshaft. BUG= R=weiliang.lin@intel.com Review URL: https://codereview.chromium.org/399313005 Patch from Chunyang Dai <chunyang.dai@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22459 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 17 Jul, 2014 19 commits
-
-
balazs.kilvady@imgtec.com authored
MIPS: StubCallInterfaceDescriptor and CallInterfaceDescriptor are unified under a base class InterfaceDescriptor. Port r22448 (a9e0b0e) Original commit message: Handling of the context register had to be massaged to effect the unification. This will make it easier to call hydrogen code stubs directly from crankshaft. BUG= R=mvstanton@chromium.org, paul.lind@imgtec.com Review URL: https://codereview.chromium.org/400743002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22456 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
The paths for some of the Windows-specific files was incorrect. R=jochen@chromium.org Review URL: https://codereview.chromium.org/402693002 Patch from Brett Wilson <brettw@chromium.org>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22455 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
This reverts r22452. TBR=amikhaylova@google.com Review URL: https://codereview.chromium.org/399963002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22454 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=verwaest@chromium.org Review URL: https://codereview.chromium.org/393313003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22453 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
BUG=v8:3291 LOG=N R=aandrey@chromium.org, yangguo@chromium.org Review URL: https://codereview.chromium.org/398513005 Patch from Alexandra Mikhaylova <amikhaylova@google.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22452 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/397073004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22451 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ernstm@chromium.org authored
R=hpayer@chromium.org BUG= Review URL: https://codereview.chromium.org/397953012 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22450 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/399753004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22449 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mvstanton@chromium.org authored
StubCallInterfaceDescriptor and CallInterfaceDescriptor are unified under a base class InterfaceDescriptor. Handling of the context register had to be massaged to effect the unification. This will make it easier to call hydrogen code stubs directly from crankshaft. R=danno@chromium.org Review URL: https://codereview.chromium.org/384403002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22448 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
This is just cosmetic: We usually avoid using %FunctionSetLength. R=dslomov@chromium.org Review URL: https://codereview.chromium.org/400583002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22447 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
The WebView Mac builder is having trouble with resolving set_at_offset with an intptr_t argument to the correct overload. Add back the static_cast which was present before r22293 to resolve this. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/398893003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22446 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
Three fixes which are required to pass all the tests when out-of-line constant pools are enabled for Arm: - Invalidate embedded objects in optimized code when it is deoptimized such that the weak pointers in the constant pool array are cleared. This prevents a CHECK(heap_->mark_compact_collector()->IsMarked(object)) error when a verifying weak pointers in a deoptimized code object's constant pool. - Modify LargeObjectSpace::Verify to allow constant pool arrays in the large object space. - Increase the 32bit stack size limit, since the constant pool pointer is now on every stack frame, causing the size of each stack frame to increase by one word, and causing deep-recursion-test to fail. R=hpayer@chromium.org Review URL: https://codereview.chromium.org/385163005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22445 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rmcilroy@chromium.org authored
The current gyp config tries to test whether the compiler is an arm / mips compiler and whether it supports -m32 / -m64 based on a test within gyp. Unfortunately CXX / CXX_target / CXX_host are no no longer set early enough in gyp for this to work, and so all of these tests were actually being done using "$(which g++)" rather than the appropriate CXX_target / CXX_host compiler. This change removes these dynamic tests and instead bases the decisions on knowledge of the host / target / v8_target architecture combination. The the -m32/-m64 flags are set based on host_cxx_is_biarch / target_cxx_is_biarch, which are set to reasonable defaults of only ia32/x64 or clang compilers being build for biarch support. The host_cxx_is_biarch / target_cxx_is_biarch variables can be overriden if required. Original Review URL: https://codereview.chromium.org/382343003 TBR=jkummerow@chromium.org BUG=384474 LOG=NO Review URL: https://codereview.chromium.org/400573002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22444 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rodolph.perfetta@arm.com authored
BUG=v8:3444 TEST=mjsunit/regress/regress-regexp-nocase.js LOG=N R=yangguo@chromium.org Review URL: https://codereview.chromium.org/392403002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22443 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
BUG=none R=verwaest@chromium.org LOG=n Review URL: https://codereview.chromium.org/390323002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22442 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
verwaest@chromium.org authored
The only case in which the hole can still occur, is in a pre-allocated PropertyCell in a GlobalObject. In that case it indicates that the property is absent. BUG= R=ishell@chromium.org Review URL: https://codereview.chromium.org/389353002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22441 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=verwaest@chromium.org Review URL: https://codereview.chromium.org/396993004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22440 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ernstm@chromium.org authored
- Split GCTracer::~GCTracer into printing functions and update of variables tracked on Heap. - Clean-up recording of time, object size and memory size at the beginning and end of GC. - Consistently use enum notation in ScopeId. - Disallow copy and assign for Scope and GCTracer. - Remove unused stats on GCTracer. R=hpayer@chromium.org BUG= Review URL: https://codereview.chromium.org/396893004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22439 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
BUG=v8:3446 LOG=N TBR=hpayer@chromium.org Review URL: https://codereview.chromium.org/400533002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22438 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 16 Jul, 2014 8 commits
-
-
yangguo@chromium.org authored
TBR=jochen@chromium.org Review URL: https://codereview.chromium.org/397463004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22435 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=rossberg@chromium.org BUG=v8:2938 LOG=Y Review URL: https://codereview.chromium.org/394833002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22434 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=hpayer@chromium.org Review URL: https://codereview.chromium.org/392163003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22433 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ernstm@chromium.org authored
longest_step is only output at the end of a mark-compact. We shouldn't reset it after a Scavenge. R=hpayer@chromium.org BUG= Review URL: https://codereview.chromium.org/395153003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22432 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
vogelheim@chromium.org authored
(parser or code) and to be explicit about cache consumption or production (rather than making presence of cached_data imply one or the other.) Also add a --cache flag to d8, to allow testing the functionality. ----------------------------- API change Reason: Currently, V8 supports a 'parser cache' for repeatedly executing the same script. We'd like to add a 2nd mode that would cache code, and would like to let the embedder decide which mode they chose (if any). Note: Previously, the 'use cached data' property was implied by the presence of the cached data itself. (That is, kNoCompileOptions and source->cached_data != NULL.) That is no longer sufficient, since the presence of data is no longer sufficient to determine /which kind/ of data is present. Changes from old behaviour: - If you previously didn't use caching, nothing changes. Example: v8::CompileUnbound(isolate, source, kNoCompileOptions); - If you previously used caching, it worked like this: - 1st run: v8::CompileUnbound(isolate, source, kProduceToCache); Then, source->cached_data would contain the data-to-be cached. This remains the same, except you need to tell V8 which type of data you want. v8::CompileUnbound(isolate, source, kProduceParserCache); - 2nd run: v8::CompileUnbound(isolate, source, kNoCompileOptions); with source->cached_data set to the data you received in the first run. This will now ignore the cached data, and you need to explicitly tell V8 to use it: v8::CompileUnbound(isolate, source, kConsumeParserCache); ----------------------------- BUG= R=marja@chromium.org, yangguo@chromium.org Review URL: https://codereview.chromium.org/389573006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22431 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=verwaest@chromium.org Review URL: https://codereview.chromium.org/397973002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22430 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/395823002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22429 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
machenbach@chromium.org authored
This allows benchmarks to contain regular expression characters in their name. BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/396203003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22428 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-