Cycles: Wrap spatial split storage into own structure
authorSergey Sharybin <sergey.vfx@gmail.com>
Sun, 21 Feb 2016 14:39:02 +0000 (15:39 +0100)
committerSergey Sharybin <sergey.vfx@gmail.com>
Thu, 31 Mar 2016 08:06:21 +0000 (10:06 +0200)
commitbbbbe68473e02567a902a6405ca09de216674615
tree0e6dd43ed39c091bfac7001e636612e2136ea202
parent9c420e5e481f00f42eeea42979c140afc8ee4acc
Cycles: Wrap spatial split storage into own structure

This has following advantages:

- Localizes all the run-time storage into a single structure,
  which could easily be extended further.

- Storage could be created per-thread, so once builder is
  threaded we wouldn't have any conflicts between threads.

- Global nature of the storage avoids memory re-allocation
  on the runtime, keeping builder as fast as possible.

Currently it's just API changes, which don't affect user at all.
intern/cycles/bvh/bvh_build.cpp
intern/cycles/bvh/bvh_build.h
intern/cycles/bvh/bvh_params.h
intern/cycles/bvh/bvh_split.cpp
intern/cycles/bvh/bvh_split.h