News for hackers. Stuff that matters.
Re:Mid-stack inlining in the Go compiler by kevincox on Monday March 06, 2017 @02:47PM (#13805465)
If I'm understanding the increase is mostly due to the "debugging" info that is added, not necessarily due to more code.
Re:Mid-stack inlining in the Go compiler by DannyBee on Monday March 06, 2017 @03:04PM (#13805597)
I strongly doubt this. It doesn't say this in the preso, and ...

1. The compiler is a lot slower, which is usually from code growth and not debugging info growth. If the compiler is that much slower from debugging info growth, they have larger issues :) 2. Usually people do not include debug info sizes in binary sizes, because DWARF/et al info can be stripped and put alongside the binary (IE it doesn't even have to be part of the binary)

Re:Mid-stack inlining in the Go compiler by sythe2o0 on Monday March 06, 2017 @06:29PM (#13807062)
It does say this. One of the last slides says 4% of the additional size came from adding more debugging information, excluding anything to do with the new inlining.
Re:Mid-stack inlining in the Go compiler by DannyBee on Tuesday March 07, 2017 @09:36PM (#13817374)
"If I'm understanding the increase is mostly due to the "debugging" info that is added, not necessarily due to more code. " vs " One of the last slides says 4% of the additional size came from adding more debugging information, excluding anything to do with the new inlining"

So no, it doesn't say that it's "mostly due", it says ~25% is due to debugging information.