[Eager] fix recompute for stop_gradient and inpalce #48471
Merged
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.
PR types
Bug fixes
PR changes
Others
Describe
Fix recompute for stop_gradient and inpalce.
In some cases a subset of outputs is identity to the subset of inputs, which is inplace operating. When the inputs' stop_gradient is True, an error will occurs because the stop_gradient=True and inpalce-op are not supported at the same time. The solution is to mark the inputs non_differentiable if its stop_gradient is True.
attribute
stop gradient
will be reset toFalse
in c++ backend . code:Paddle/paddle/fluid/pybind/eager_py_layer.cc
Line 388 in 9d62efb