Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Dy2stat]Fix error when calling sublayer's non-forward func in dy2stat #37296

Merged
merged 10 commits into from
Dec 24, 2021

Conversation

0x45f
Copy link
Contributor

@0x45f 0x45f commented Nov 17, 2021

PR types

Bug fixes

PR changes

Others

Describe

Fix error when calling sublayer's non-forward func in dy2stat

@paddle-bot-old
Copy link

Thanks for your contribution!
Please wait for the result of CI firstly. See Paddle CI Manual for details.

@paddle-bot-old
Copy link

Sorry to inform you that 052a8d2's CIs have passed for more than 7 days. To prevent PR conflicts, you need to re-run all CIs manually.

Copy link
Contributor

@Aurelius84 Aurelius84 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Aurelius84 Aurelius84 merged commit 7339a12 into PaddlePaddle:develop Dec 24, 2021
0x45f added a commit to 0x45f/Paddle that referenced this pull request Dec 24, 2021
PaddlePaddle#37296)

* fix error when calling sublayer's non-forward func in dy2stat

* fix circular import using an inelegant way

* deal with parameters

* remove param_guard in __call__

* remove comment

* fix error when jit.load

* rename block var

* remove wrong code

* add unit test
lanxianghit pushed a commit that referenced this pull request Jan 5, 2022
… in dy2stat (#38418)

Fix error when calling sublayer's non-forward func in dy2stat
cherrypick: #37713#37759#37296#38540#37888
@0x45f 0x45f deleted the dy2stat_tensor_mul branch January 10, 2022 07:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants