96edc24598
Reason for revert: Chrome's side of define changes not easy to figure out quickly. Reverting this for DEPS roll for now. Original issue's description: > Rename kPMColor_SkColorType to kN32_SkColorType. > > The new name better represents what this flag means. > > BUG=skia:2384 > > Committed: http://code.google.com/p/skia/source/detail?r=14117 R=reed@google.com, scroggo@google.com TBR=reed@google.com, scroggo@google.com NOTREECHECKS=true NOTRY=true BUG=skia:2384 Author: bensong@google.com Review URL: https://codereview.chromium.org/234833003 git-svn-id: http://skia.googlecode.com/svn/trunk@14149 2bbb7eff-a529-9590-31e7-b0007b416f81 |
||
---|---|---|
.. | ||
DM.cpp | ||
DMBenchTask.cpp | ||
DMBenchTask.h | ||
DMCpuGMTask.cpp | ||
DMCpuGMTask.h | ||
DMExpectations.h | ||
DMExpectationsTask.cpp | ||
DMExpectationsTask.h | ||
DMGpuGMTask.cpp | ||
DMGpuGMTask.h | ||
DMGpuSupport.h | ||
DMPipeTask.cpp | ||
DMPipeTask.h | ||
DMRecordTask.cpp | ||
DMRecordTask.h | ||
DMReplayTask.cpp | ||
DMReplayTask.h | ||
DMReporter.cpp | ||
DMReporter.h | ||
DMSerializeTask.cpp | ||
DMSerializeTask.h | ||
DMTask.cpp | ||
DMTask.h | ||
DMTaskRunner.cpp | ||
DMTaskRunner.h | ||
DMTestTask.cpp | ||
DMTestTask.h | ||
DMTileGridTask.cpp | ||
DMTileGridTask.h | ||
DMUtil.cpp | ||
DMUtil.h | ||
DMWriteTask.cpp | ||
DMWriteTask.h | ||
README |
DM is like GM, but multithreaded. It doesn't do everything GM does yet. Current approximate list of missing features: --config pdf --mismatchPath --missingExpectationsPath --writePicturePath --deferred DM's design is based around Tasks and a TaskRunner. A Task represents an independent unit of work that might fail. We make a task for each GM/configuration pair we want to run. Tasks can kick off new tasks themselves. For example, a CpuTask can kick off a ReplayTask to make sure recording and playing back an SkPicture gives the same result as direct rendering. The TaskRunner runs all tasks on one of two threadpools, whose sizes are configurable by --cpuThreads and --gpuThreads. Ideally we'd run these on a single threadpool but it can swamp the GPU if we shove too much work into it at once. --cpuThreads defaults to the number of cores on the machine. --gpuThreads defaults to 1, but you may find 2 or 4 runs a little faster. So the main flow of DM is: for each GM: for each configuration: kick off a new task < tasks run, maybe fail, and maybe kick off new tasks > wait for all tasks to finish report failures