search for: sizeinfo

Hi folks, Sometimes I make a change to the compiler that causes a binary size regression and I need to track down where that regression came from. One relatively naive way of doing this is to take two build trees, one compiled with the old compiler and another compiled with the new compiler, and then compare the symbol sizes (st_size) in the final output files in each build tree. The problem with

...'s enough interest I can explore using an alternative format for visualization, e.g: http://neugierig.org/software/chromium/bloat/ https://github.com/evmar/webtreemap (Thanks JF for pointing these out!) Here's a link to the source code: https://github.com/vedantk/llvm-project/tree/sizeinfo Selected Examples ----------------- Here are a few interesting snippets from a comparison of clang-6 vs. clang-7. First, let's take a look at the function view diffstat. Here are the 10 functions which grew in size the most. On the left hand side, you'll see the demangled function name...

...oat/ <http://neugierig.org/software/chromium/bloat/> > https://github.com/evmar/webtreemap <https://github.com/evmar/webtreemap> > > (Thanks JF for pointing these out!) > > Here's a link to the source code: > > https://github.com/vedantk/llvm-project/tree/sizeinfo <https://github.com/vedantk/llvm-project/tree/sizeinfo> > > Selected Examples > ----------------- > > Here are a few interesting snippets from a comparison of clang-6 vs. clang-7. > > First, let's take a look at the function view diffstat. Here are the 10 > fu...

...g/software/chromium/bloat/> >> https://github.com/evmar/webtreemap <https://github.com/evmar/webtreemap> >> >> (Thanks JF for pointing these out!) >> >> Here's a link to the source code: >> >> https://github.com/vedantk/llvm-project/tree/sizeinfo <https://github.com/vedantk/llvm-project/tree/sizeinfo> >> >> Selected Examples >> ----------------- >> >> Here are a few interesting snippets from a comparison of clang-6 vs. clang-7. >> >> First, let's take a look at the function view diffs...