Cycles: Experiment with use of runtime tag instead of set for SVM generation
This gives about 2x speedup (3.2sec vs. 11.9sec with 32716 handled nodes) when updating shader for the shader tree. Reviewers: brecht, juicyfruit, dingto, lukasstockner97 Differential Revision: https://developer.blender.org/D1700
This commit is contained in:
@@ -154,11 +154,26 @@ protected:
|
||||
|
||||
/* Global state of the compiler accessible from the compilation routines. */
|
||||
struct CompilerState {
|
||||
CompilerState(ShaderGraph *graph);
|
||||
|
||||
/* ** Global state, used by various compilation steps. ** */
|
||||
|
||||
/* Set of nodes which were already compiled. */
|
||||
ShaderNodeSet nodes_done;
|
||||
|
||||
/* Set of closures which were already compiled. */
|
||||
ShaderNodeSet closure_done;
|
||||
|
||||
/* ** SVM nodes generation state ** */
|
||||
|
||||
/* Flag whether the node with corresponding ID was already compiled or
|
||||
* not. Array element with index i corresponds to a node with such if.
|
||||
*
|
||||
* TODO(sergey): This is actually a copy of nodes_done just in another
|
||||
* notation. We can de-duplicate this storage actually after switching
|
||||
* all areas to use this flags array.
|
||||
*/
|
||||
vector<bool> nodes_done_flag;
|
||||
};
|
||||
|
||||
void stack_backup(StackBackup& backup, ShaderNodeSet& done);
|
||||
|
Reference in New Issue
Block a user