[AutoDiff] Don't propagate activity through '@noDerivative' projections. #27472
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reads or writes to
@noDerivativeproperties of struct should not be differentiated. At the implementation level, this amounts to not propagating activity through@noDerivativeprojections. This has been done in some of usefulness propagation, but there are two places where this has not been done:DifferentiableActivityInfo::propagateUsefulThroughBuffer, usefulness was being propagated arbitrarily regardless of the instruction.DifferentiableActivityInfo::recursivelySetVaried, variedness was set regardless of whether the proejction is a@noDerivativeone.This patch changes activity analysis to not propagate activity through
@noDerivativefield projections from a struct, covering both previously uncovered places discussed above. As a result,PullbackEmitter::getAdjointBufferno longer needs to check for@noDerivativeor emit any diagnostics.Resolves TF-865.