- 01 Jun, 2015 1 commit
-
-
erikcorry authored
When compiling on a laptop I like to concatenate the small test files. This makes a big difference to compile times. These changes make that easier. R=ulan@chromium.org BUG= Review URL: https://codereview.chromium.org/1163803002 Cr-Commit-Position: refs/heads/master@{#28742}
-
- 29 May, 2015 1 commit
-
-
jarin authored
BUG= Review URL: https://codereview.chromium.org/1148293009 Cr-Commit-Position: refs/heads/master@{#28697}
-
- 20 May, 2015 1 commit
-
-
mstarzinger authored
This flag mostly duplicates SharedFunctionInfo::optimization_disabled and is only queried in places where the original is available. Remove the brittle and error-prone duplication. R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/1148043002 Cr-Commit-Position: refs/heads/master@{#28520}
-
- 15 May, 2015 1 commit
-
-
jochen authored
We want to move to a world where there's no Isolate::Current but we always knows which isolate we're in. There's no way we can teach this info to the C++ allocator. BUG=none R=hpayer@chromium.org LOG=n Review URL: https://codereview.chromium.org/1128023005 Cr-Commit-Position: refs/heads/master@{#28414}
-
- 28 Apr, 2015 1 commit
-
-
ofrobots authored
assertion did match the conditions under which this method gets called (Runtime_DateCurrentTime). The bug got introduced as part of this change: https://codereview.chromium.org/802333002 The assertion crash can be reproduced using: % out/Debug/d8 --prof -e 'new Date();' R=jkummerow@chromium.org BUG= Review URL: https://codereview.chromium.org/1104303002 Cr-Commit-Position: refs/heads/master@{#28096}
-
- 27 Mar, 2015 1 commit
-
-
yangguo authored
R=jochen@chromium.org Review URL: https://codereview.chromium.org/1041743002 Cr-Commit-Position: refs/heads/master@{#27501}
-
- 09 Mar, 2015 1 commit
-
-
loislo authored
The original code always returned the first entry from RelocInfo that matched with bailout_id. But we may have a few different deopt reasons for one bailout_id. So we need to get the one which matches with a particular call from JumpTable. We can do this by checking not 'target_address' (it maps to bailout_id) but 'from' address which maps to a particular JumpTable entry. The test was reworked so it tests identical functions against different reasons. BUG=chromium:452067 LOG=n Review URL: https://codereview.chromium.org/984773003 Cr-Commit-Position: refs/heads/master@{#27076}
-
- 03 Mar, 2015 1 commit
-
-
sejunho authored
Problem: Excuting with flags as "--prof --logfile-per-isolate --logfile=/path/to/filename" expected file name: /path/to/isolate-<isolate id>-filename current result: isolate-<isolate id>-/path/to/filename This patch makes the file name we expected. Review URL: https://codereview.chromium.org/960813004 Cr-Commit-Position: refs/heads/master@{#26955}
-
- 26 Feb, 2015 1 commit
-
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/942963004 Cr-Commit-Position: refs/heads/master@{#26874}
-
- 20 Feb, 2015 1 commit
-
-
loislo authored
We accessed to cpu_profiler for tracking SharedFunctionInfo objects movements and used their addresses for generating function_id. Actually we could replace the manually generated shared_id by the pair script_id + position. In this case we can drop SharedFunctionInfo events support from cpu_profiler and remove the dependency. BTW GetCallUid was used as an unique identifier of the function on the front-end side. Actually it is a hash which might not be unique. So I renamed GetCallUid with GetHash and implemented GetFunctionId method. BUG=452067 LOG=n Review URL: https://codereview.chromium.org/941973002 Cr-Commit-Position: refs/heads/master@{#26775}
-
- 10 Feb, 2015 1 commit
-
-
loislo authored
1) Deoptimizer::Reason was replaced with Deoptimizer::DeoptInfo because it also has raw position. Also the old name clashes with DeoptReason enum. 2) c_entry_fp assignment call was added to EntryGenerator::Generate So we can calculate sp and have a chance to record the stack for the deopting function. btw it makes the test stable. 3) new kind of CodeEvents was added to cpu-profiler 4) GetDeoptInfo method was extracted from PrintDeoptLocation. So it could be reused in cpu profiler. BUG=452067 LOG=n Review URL: https://codereview.chromium.org/910773002 Cr-Commit-Position: refs/heads/master@{#26545}
-
- 30 Jan, 2015 3 commits
-
-
bmeurer authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/877753007 Cr-Commit-Position: refs/heads/master@{#26346}
-
Benedikt Meurer authored
This reverts commit 6a4c0a3b and commit 0deaa4b6 for breaking GCC bots. TBR=svenpanne@chromium.org Review URL: https://codereview.chromium.org/893533003 Cr-Commit-Position: refs/heads/master@{#26342}
-
bmeurer authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/888613002 Cr-Commit-Position: refs/heads/master@{#26340}
-
- 20 Jan, 2015 1 commit
-
-
jkummerow authored
(1) --prof-cpp: Collects ticks like --prof, but ignores code creation events to reduce distortion (so all JS ticks will be "unaccounted"). Useful for profiling C++ code. (2) --timed-range flag for tick processor: Ignores ticks before the first and after the last call to Date.now(). Useful for focusing on the timed section of a test. Review URL: https://codereview.chromium.org/802333002 Cr-Commit-Position: refs/heads/master@{#26168}
-
- 16 Jan, 2015 1 commit
-
-
Sven Panne authored
Contribution of PowerPC port (continuation of 422063005). The inital patch covers the core changes to the common files. Subsequent patches will cover changes to common files to support AIX and to update the ppc directories so they are current with the changes in the rest of the project. This is based off of the GitHub repository https://github.com/andrewlow/v8ppc BUG= R=svenpanne@chromium.org, danno@chromium.org, sevnpanne@chromium.org Review URL: https://codereview.chromium.org/817143002 Cr-Commit-Position: refs/heads/master@{#26091}
-
- 13 Nov, 2014 1 commit
-
-
Andy Wingo authored
R=svenpanne@chromium.org Review URL: https://codereview.chromium.org/668143003 Cr-Commit-Position: refs/heads/master@{#25321}
-
- 14 Oct, 2014 1 commit
-
-
yangguo@chromium.org authored
This broke because the optimizing compiler thread no longer holds Isolate::Current() in its TLS. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/655813002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24607 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Oct, 2014 1 commit
-
-
jochen@chromium.org authored
It's used from multiple threads BUG=none R=yangguo@chromium.org LOG=n Review URL: https://codereview.chromium.org/640773002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24480 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 08 Oct, 2014 2 commits
-
-
jochen@chromium.org authored
BUG=none TBR=ishell@chromium.org LOG=n Review URL: https://codereview.chromium.org/638943002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24470 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
it's used on several threads BUG=none R=svenpanne@chromium.org LOG=n Review URL: https://codereview.chromium.org/639763002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24465 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 30 Sep, 2014 1 commit
-
-
bmeurer@chromium.org authored
Review URL: https://codereview.chromium.org/618643002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24319 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 24 Sep, 2014 1 commit
-
-
yangguo@chromium.org authored
R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/596783002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24161 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 17 Sep, 2014 1 commit
-
-
titzer@chromium.org authored
Rename Runtime_CompileUnoptimized to Runtime_CompileLazy, because that is what it does. Split Compiler::GetUnoptimizedCode into two variants, one for lazy compilation (which can return optimized code!) and the other that actually returns unoptimized code. R=mstarzinger@chromium.org BUG= Review URL: https://codereview.chromium.org/547293004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24012 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 12 Aug, 2014 1 commit
-
-
mstarzinger@chromium.org authored
R=jochen@chromium.org Review URL: https://codereview.chromium.org/462033002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23081 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 04 Aug, 2014 1 commit
-
-
bmeurer@chromium.org authored
This way we don't clash with the ASSERT* macros defined by GoogleTest, and we are one step closer to being able to replace our homegrown base/ with base/ from Chrome. R=jochen@chromium.org, svenpanne@chromium.org Review URL: https://codereview.chromium.org/430503007 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22812 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 16 Jul, 2014 1 commit
-
-
yangguo@chromium.org authored
R=fmeawad@chromium.org Review URL: https://codereview.chromium.org/388783004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22422 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 15 Jul, 2014 1 commit
-
-
danno@chromium.org authored
During https://code.google.com/p/v8/source/detail?r=19925 checkin context bound scripts (Script) and context unbound scripts (UnboundScript) are Distinguished. And then Sven Panne helped to fix the vtune support compilation error in https://code.google.com/p/v8/source/detail?r=20955. The problem is that there is runtime error for vtune support. In our original implementation, we encapsulated and passed v8::internal::Script to V8 API. It will leads to type check error for current V8::Script definition. So I changed the Handle<Script> definition in JitCodeEvent to Handle<UnboundScript> and add the corresponding change in log.cc. If you do NOT prefer to change in include/v8.h. I think I can change the definition of CodeEventLogger::LogRecordedBuffer(...) so that the we can pass the correct type (JSFunction) as V8::Script to V8 API. BUG= R=danno@chromium.org, svenpanne@chromium.org Review URL: https://codereview.chromium.org/334263018 Patch from Chunyang Dai <chunyang.dai@intel.com>. git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22393 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 14 Jul, 2014 1 commit
-
-
yangguo@chromium.org authored
Currently this does not happen if the message builder buffer is full. R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/390803002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22368 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 03 Jul, 2014 2 commits
-
-
jarin@chromium.org authored
Bringing the offending timer functions to the platform dependent files. BUG= R=yangguo@chromium.org Review URL: https://codereview.chromium.org/367033002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22210 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
Note that until everything is OStream-based, there are a few places where we have to do some impedance matching. A few accessors had to be const-corrected on the way. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/334763003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22179 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 02 Jul, 2014 2 commits
-
-
yangguo@chromium.org authored
This reverts r22146. TBR=jarin@chromium.org Review URL: https://codereview.chromium.org/366883004 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22150 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jarin@chromium.org authored
This disables the perf support in Android because of build problems with librt (should be fixable with a bit of effort, but priority is low). BUG= R=yangguo@chromium.org Review URL: https://codereview.chromium.org/360783006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22146 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 01 Jul, 2014 2 commits
-
-
jarin@chromium.org authored
Android ninja build still failing. TBR=yangguo@chromium.org Review URL: https://codereview.chromium.org/367633003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22119 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jarin@chromium.org authored
This relands r22098. BUG= R=yangguo@chromium.org Review URL: https://codereview.chromium.org/368433006 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22118 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 30 Jun, 2014 3 commits
-
-
jochen@chromium.org authored
GetCurrentThreadId doesn't compile on android Also reverts follow up build fix attempts BUG=none LOG=n TBR=jarin@chromium.org Review URL: https://codereview.chromium.org/337093005 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22104 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jarin@chromium.org authored
This adds timestamps to allow profiling with code space reuse. Also a couple of updates to reflect the changes in the JIT perf interface + a move of the perf-related stuff into separate files. Unfortunately, the change only works with the latest patch to the perf tool from a Linux perf tool contributor (Stephane Eranian). BUG= R=yangguo@chromium.org Review URL: https://codereview.chromium.org/255803003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22098 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jochen@chromium.org authored
Also split v8-core independent methods from checks.h to base/logging.h and merge v8checks with the rest of checks. The CPU::FlushICache method is moved to CpuFeatures::FlushICache RoundUp and related methods are moved to base/macros.h Remove all layering violations from src/libplatform BUG=none R=jkummerow@chromium.org LOG=n Review URL: https://codereview.chromium.org/358363002 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22092 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 24 Jun, 2014 2 commits
-
-
alph@chromium.org authored
LOG=N R=jkummerow@chromium.org, loislo@chromium.org, yurys@chromium.org Review URL: https://codereview.chromium.org/357443003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21986 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
baptiste.afsa@arm.com authored
R=ulan@chromium.org Review URL: https://codereview.chromium.org/353643003 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@21965 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-