Re: Default value for FULL_OPTIMIZATION

[Phil Blundell <pb@pbcl.net>]

On Tue, 2016-02-02 at 14:26 +0100, Pascal Bach wrote:
> I'm not sure if the documentation is wrong or if the default set in bitbake.conf is incorrect.
> Maybe somebody can shed some light on this.

FULL_OPTIMIZATION in bitbake.conf did use to match what the
documentation says (or at least, was much closer to it).  It was changed
to the current value by commit 9cb71137 which apparently omitted to
update the documentation. 

As an aside, this commit also added "-pipe" to both FULL_OPTIMIZATION
and DEBUG_OPTIMIZATION, which seems a bit weird since (a) -pipe doesn't
have any effect on the generated code; and (b) if it's going to enabled
for both debug and release builds then it might as well go in ${CC} or
somewhere.  Also, that commit seems to have deliberately turned down the
level of optimisation somewhat in order to facilitate debugging, which
is perhaps not what folks who request FULL_OPTIMIZATION would expect.

But anyway, irrespective of the detailed merits or otherwise of that
patch, I think that updating the documentation to match what the code is
now doing would be a fine idea.

p.