On 09/26/2017 12:17 PM, Eric Botcazou wrote:
By the way, why not always do this "inlining", even when not optimizing?
Because this generates more bloated code and inferior debugging experience.
This is a trick question, because when you answer "because XYZ" I will then
reply "but XYZ is a common reason that people disable inlining when
optimizing, so shouldn't you only do it when inlining is enabled?" :)
People ought not to disable inlining when optimizing though.
I've seen a few projects disable inlining when optimizing because it can
generate bloated code and an inferior debugging experience :) But I won't argue
the point any further (that this should really be conditioned on inlining being
enabled, not on optimization being enabled) as while I'm probably right in
theory, in practice I doubt it will actually cause trouble for anyone.
Best wishes, Duncan.
