|author||Ian Romanick <firstname.lastname@example.org>||2013-05-08 10:59:47 -0700|
|committer||Ian Romanick <email@example.com>||2013-05-13 12:05:19 -0700|
glsl: Remove some stale comments about ir_call
ir_call was changed long ago to be a statement rather than an expression. That makes this comment no longer valid. Signed-off-by: Ian Romanick <firstname.lastname@example.org> Reviewed-by: Kenneth Graunke <email@example.com> Reviewed-by: Paul Berry <firstname.lastname@example.org>
Diffstat (limited to 'src')
1 files changed, 2 insertions, 6 deletions
diff --git a/src/glsl/lower_clip_distance.cpp b/src/glsl/lower_clip_distance.cpp
index 2ba0052e05..129375d665 100644
@@ -226,12 +226,8 @@ lower_clip_distance_visitor::visit_leave(ir_assignment *ir)
* each of them.
* Note: to unroll into element-by-element assignments, we need to make
- * clones of the LHS and RHS. This is only safe if the LHS and RHS are
- * side-effect free. Fortunately, we know that they are, because the
- * only kind of rvalue that can have side effects is an ir_call, and
- * ir_calls only appear (a) as a statement on their own, or (b) as the
- * RHS of an assignment that stores the result of the call in a
- * temporary variable.
+ * clones of the LHS and RHS. This is safe because expressions and
+ * l-values are side-effect free.
void *ctx = ralloc_parent(ir);
int array_size = this->old_clip_distance_var->type->array_size();