Executable size on disk doesn't dictate effective size at higher levels of the memory hierarchy. IOW, you're paying by the page/cache line. If the extra bloat

Executable size on disk doesn't dictate effective size at higher levels of the memory hierarchy. IOW, you're paying by the page/cache line. If the extra bloat (debug information) in your executable isn't interspersed within your actual code (it shouldn't be), you aren't paying for it in runtime efficiency.