ZOzokier·Apr 2, 2018
I created https://github.com/google/bloaty/issues/110 to track this. I'll try to find time to clean up the patch, but no promises. Lets continue the discussion in the GH issue.
In Building Tiny Rust Binaries for Embedded Linuxgoogle
bloaty
C++2016–2026
google / bloaty
bloaty
Bloaty: a size profiler for binaries
20Distinct people
31Mentions
1Explicit recommenders
5.6KGitHub stars
What to know before exploring
What it is
Bloaty: a size profiler for binaries
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
Since we're talking about ELF binaries, let me drop a link for my favorite size profiler (that is compatible with ELF and other formats): Bloaty McBloatface.…
fnayr used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:19:25 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year31 dated mentions
Observed mentions: 2016-11-08 19:50:38 UTC to 2026-01-06 20:02:22 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 4 | 2 | 2 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 7 | 4 | 3 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourcesThis was easier than I thought:
https://github.com/google/bloaty/compare/master...zokier:rus...
and here is the wrapper for rustc-demangle:
https://github.com/zokier/rust-demangle-clib
Seems to work just fine for my simple use at least:
[zokier@zarch bloaty]$ ./bloaty -d sections,segments,symbols -C rust /tmp/tinyrocket/target/release/tinyrocket
VM SIZE FILE SIZE
-------------- --------------
52.0% 506Ki .text 506Ki 24.8%
100.0% 506Ki LOAD [RX] 506Ki 100.0%
65.6% 332Ki [967
Read the rest
Others] 332Ki 65.6%
5.1% 25.7Ki hyper::server::listener::spawn_with::{{closure}} 25.7Ki 5.1%
3.6% 18.3Ki <yansi::Paint<T> as core::fmt::Display>::fmt 18.3Ki 3.6%
2.9% 14.5Ki rocket::ignite 14.5Ki 2.9%
2.5% 12.8Ki rocket::config::config::Config::set_raw 12.8Ki 2.5%
2.1% 10.7Ki core::ptr::drop_in_place 10.7Ki 2.1%
1.9% 9.78Ki std::sys_common::backtrace::output 9.78Ki 1.9%
1.9% 9.62Ki tinyrocket::main 9.62Ki 1.9%
1.6% 8.16Ki <alloc::raw_vec::RawVec<T, A>>::double 8.16Ki 1.6%
...
I can try to clean it up bit more etc if you want a proper pull request for this?
> I suppose this is the end of the dive, unless someone knows some tools to get more insight into .rodata data. I suppose in theory it should be possible to track down where in the code each bit of .rodata is accessed from, but that seems bit of a stretch.
My tool Bloaty (https://github.com/google/bloaty) attempts to do exactly this. It even disassembles the binary looking for instructions that reference other sections like .rodata.
It doesn't currently know anything about Rust's name mangling scheme. I'd be happy to add this, though I suppose Rust's mangling is probably written in Rust and Bloaty is written in C++.
In Building Tiny Rust Binaries for Embedded LinuxShameless plug: my project Bloaty (https://github.com/google/bloaty) is a size profiler that shows you both mapped size and file size out-of-the-box.
In Building Tiny Rust Binaries for Embedded Linux