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

Tracking issue for dynamically linked executable size #1911

Closed
3 tasks done
bjorn3 opened this issue Apr 13, 2021 · 3 comments
Closed
3 tasks done

Tracking issue for dynamically linked executable size #1911

bjorn3 opened this issue Apr 13, 2021 · 3 comments
Labels
C-Code-Quality A section of code that is hard to understand or change C-Performance A change motivated by improving speed, memory usage or compile times

Comments

@bjorn3
Copy link
Contributor

bjorn3 commented Apr 13, 2021

This issue tracks reductions in the size of games when compiling in release mode using the "dynamic" cargo feature to dynamically link bevy with the fast compile configuration. This is the fastest incremental compilation method for the bevy examples.

History of breakout example size

@bjorn3
Copy link
Contributor Author

bjorn3 commented Apr 13, 2021

A lot of space is used for the drop glue of various types. (Edit: #1914 will make this a bit better)

@alice-i-cecile alice-i-cecile added C-Performance A change motivated by improving speed, memory usage or compile times C-Code-Quality A section of code that is hard to understand or change labels Apr 13, 2021
@Weibye
Copy link
Contributor

Weibye commented Jun 6, 2021

#1914 Has been merged. Should this issue be considered closed?

@bjorn3
Copy link
Contributor Author

bjorn3 commented Jun 6, 2021

There is no low hanging fruit anymore to improve this I think, so yes.

@bjorn3 bjorn3 closed this as completed Jun 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-Code-Quality A section of code that is hard to understand or change C-Performance A change motivated by improving speed, memory usage or compile times
Projects
None yet
Development

No branches or pull requests

3 participants