-
Notifications
You must be signed in to change notification settings - Fork 68
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
Take a stripped file and symbols as additional input #588
Comments
This would be very very helpful. At the moment following the instructions in #490 I am only able to run twiggy in modes where my binary is much larger than it is in the shipping configuration and I am not sure how to tell whether the reported sizes correspond well to the sizes in non-debug builds. For example I worry, what if I spend a lot of time optimizing function N which looks big in the dev build, but it turns out when -Os is doing its thing function N was pretty small anyway… Is there some way, if I could generate a standalone symbols file, I could look up the numbers (eg "data[31]" or "code[482]" or whatever) in the stripped Twiggy view manually? |
💡 Feature Description
Would be cool to make this work in release mode where we have a stripped file & additional symbols info (e.g. made with wasm-split).
💻 Example Usage
It would help size optimize the release-mode binaries.
The text was updated successfully, but these errors were encountered: