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

Size optimise NRF SDK build #2102

Merged
merged 1 commit into from
Sep 14, 2024
Merged

Conversation

mark9064
Copy link
Member

Currently the NRF SDK is built with -O3 rather than -Os like with everything else

This saves a bit of flash space and performance seems unchanged to me. Thoughts on this change? I could definitely see the performance improvement being justified if it exists, but I don't have a profiler or anything.

Copy link

Build size and comparison to main:

Section Size Difference
text 374328B -4572B
data 948B 0B
bss 63480B -8B

@JF002
Copy link
Collaborator

JF002 commented Sep 14, 2024

I can't remember why we specified -O3 specifically for that target. The history is not clear about that, it was changed from -Os back and forth to -O3 multiple times with many merges... :/

I guess we can merge this if you didn't notice any unwanted side-effects :)

@JF002 JF002 merged commit 975bfc5 into InfiniTimeOrg:main Sep 14, 2024
4 of 5 checks passed
@JF002 JF002 added this to the 1.15.0 milestone Sep 14, 2024
@mark9064
Copy link
Member Author

I think if we wanted to O3 a specific part it would make the most sense to do that to LVGL as that's the biggest CPU cruncher. But I haven't had time to try that yet

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