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

Are we seeing the full benefits of LTO (link-time optimization) in CFU Playground? #330

Open
tcal-x opened this issue Oct 21, 2021 · 1 comment
Assignees

Comments

@tcal-x
Copy link
Collaborator

tcal-x commented Oct 21, 2021

With the picolibc integration in LiteX, link-time optimization is possible. But I'm not sure if we are seeing the benefits in all of the software that we compile into our monolithic executable, which includes not just LiteX libraries but also the TFLM library as well as our own code (menus etc.). Performance-wise, the TFLM libraries would be key.

@kgugala , I think you reported a 20% boost from initially enabling picolibc; but as we have seen elsewhere (#324), simply changing the code layout can increase/decrease performance by +/-20% or more, so it may be difficult to analyze.

@mithro
Copy link
Contributor

mithro commented Oct 21, 2021

I wouldn't expect much change in performance -- I would expect much more significant impact on the firmware size.

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

No branches or pull requests

3 participants