-
Notifications
You must be signed in to change notification settings - Fork 22
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
328P与air001编译相同项目,flash空间大一倍之多,请求优化。 #97
Comments
32位arm占用就是这么多,编译器决定
…---原始邮件---
发件人: ***@***.***>
发送时间: 2023年12月14日(周四) 晚上9:19
收件人: ***@***.***>;
抄送: ***@***.***>;
主题: [Air-duino/Arduino-AirMCU] 328P与air001编译相同项目,flash空间大一倍之多,请求优化。 (Issue #97)
描述一下这个bug / Describe the bug
我尝试将一个应用在328p上的项目移植到AIR001上,但是328P的FLASH空间占用47%。但使用AIR001,FLASH空间超出33%.
复现步骤 / To Reproduce
已使用u8glib库例程,都可复现。
如果正常,应该是什么样 / Expected behavior
希望能够更新pack包,解决此问题,以便此MCU应用于更多场景。
截图 / Screenshots
希望能够更新pack包,解决此问题,以便此MCU应用于更多场景。
日志 / Logs
希望能够更新pack包,解决此问题,以便此MCU应用于更多场景。
系统 / System
windows7x64
PACK包版本 / Version
0.6.2
验证
检查过该问题,之前没有人提过 / Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
提供了最小可复现工程或详细的复现步骤,确保开发者可以复现 / The provided reproduction is a minimal reproducible example of the bug.
已经提供了完整的报错信息、日志、截图,没有经过删减。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
⚠ 你的Issue可能缺少了一些信息,请自觉补全,以证明issue内容的真实性: ⚠ Your issue may be missing some information, please complete it to prove the authenticity of the content of the issue:
|
可以考虑开启 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
描述一下这个bug / Describe the bug
我尝试将一个应用在328p上的项目移植到AIR001上,但是328P的FLASH空间占用47%。但使用AIR001,FLASH空间超出33%.
复现步骤 / To Reproduce
已使用u8glib库例程,都可复现。
如果正常,应该是什么样 / Expected behavior
希望能够更新pack包,解决此问题,以便此MCU应用于更多场景。
截图 / Screenshots
希望能够更新pack包,解决此问题,以便此MCU应用于更多场景。
日志 / Logs
希望能够更新pack包,解决此问题,以便此MCU应用于更多场景。
系统 / System
windows7x64
PACK包版本 / Version
0.6.2
验证
The text was updated successfully, but these errors were encountered: