-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[Bug] [Parameter Context] The problem of global parameter priority #8329
Comments
Search before asking
What happenedIn the kai fa we development document, the global parameter localParam has the lowest priority, as shown in the figure What you expected to happenFinally print out the value of x should be lll in varpool, not 2 in localparam How to reproduceIt can be reproduced according to my definition above Anything elseNo response Version2.0.2 Are you willing to submit PR?
Code of Conduct
|
Hi:
|
我已经修改了问题,提交了pr,暂时还没有得到回复! |
I am not sure this issue is bug for code or for document, could you please take a look? @lenboo @caishunfeng . I think is it important for both codebase or document bug, so I add label |
IMO, I thinks it more like our documentation is out up date, and should be upgrade |
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs. |
Remove stale |
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs. |
PTAL @Tianqi-Dotes |
the 2.0.5 and version below 2.0.5 doc illustrate the wrong priorities, please check the dev doc. Have fixed both the doc and code,please refer to following: |
Search before asking
What happened
在kai fa we开发文档中,全局参数localParam的优先级是最低的,如图
我在测试中发现,localParam会优先级更高,下图是测试结果
What you expected to happen
最后打印出x的值应该为varpool中的lll,而不是localparam中的2
How to reproduce
按照我上面的定义即可以重新复现
Anything else
No response
Version
2.0.2
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: