SizeBench: A new tool for analyzing Windows binary size
devblogs.microsoft.com
devblogs.microsoft.com
He should have asked me, I did a lot of thiswhile I was on the Windows Phone compiler team! :-D
I spent a lot of time with dumpbin, learning how to find inefficiencies or even outright code generation bugs in the ARM compiler.
My best find was 14 extra bytes inserted after every function, IIRC it was originally to work around a bug on MIPS16 but it ended up getting added to code generation across all platforms.
It is nice someone has improved dumpbin and added some more features, and a nice UI. "New hire in office looking at object file dumps" wasn't really scalable, though I did my best!
Approximate size: 276 MB
looks like they should try running this tool on itself? $ yay -Qi xdiskusage|grep Size
Installed Size : 54.77 KiB
> it doesn't even use the c std library.isn't that expected of win32 applications? {kernel,user}32.dll typically provide the equivalent functionality.
In C++, compile times sometimes explode if you include every header in every other one - so it's really great when you can #include just a one-line generic "virtual" callback interface from two places instead.
But yes it affects binary size just a bit.