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

add v1.6 article #302

Closed
wants to merge 1 commit into from
Closed

add v1.6 article #302

wants to merge 1 commit into from

Conversation

narimiran
Copy link
Member

@narimiran narimiran commented Sep 30, 2021

This one supersedes #301.

The binary size can be further reduced to 49K with stripping `--passL:-s`
and link-time optimization (`--passC:-flto`).
Statically linking against `musl` brings it down to 5K, see
[link](https://irclogs.nim-lang.org/07-07-2020.html#12:31:34).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I've said in the original PR, I'm not sure if we should link that exact discussion - it uses some tricks like --os:any -d:posix or -d:noSignalHandler

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are not "tricks", it's things you can easily find out if you need to really care and if it's not about a silly pissing contest. I would phrase it differently though or remove it altogether. It matters for embedded development, so measure it for an embedded target...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not link to this instead? https://hookrace.net/blog/nim-binary-size/

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dom96 this is pretty outdated (we have os:any now for example) and really specific to IMO

@narimiran
Copy link
Member Author

narimiran commented Oct 4, 2021

Superseded by #304. (And the original PR by @timotheecour is now merged (but not published on the website))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants