[OE-core] [master][dora][PATCH 1/2] perf: disallow debug optimization.

[Phil Blundell]

On Thu, 2013-11-21 at 08:47 -0600, Mark Hatle wrote:
> We have users who desire to build their system at different levels of 
> optimizations for debug, size, profiling, etc.  So they do change the default 
> optimization levels from -O2 to -O0, etc.  The python fragement is used to only 
> adjust -O0, as -O1 (or -Os) work correctly.

Sure, I understand what the python is doing.  The things I'm not quite
so clear about are:

a) If the user asks to build with -O0, is it appropriate for the
metadata to second-guess this and quietly switch to using -O2 instead
when it thinks it knows best?  

Personally I am inclined to say that attempting to use -O0 with packages
that don't support it should just produce an error and the user should
fix their configuration to not do that.  And, if we're going to enable
optimisation that the user hasn't asked for, shouldn't it be the minimum
level consistent with getting the package to build rather than the full
-O2 set?

b) If the answer to (a) is that the metadata should indeed be doing
this, can it be made to do so in a way that doesn't involve running
extra python fragments for all users every time the recipe is parsed?

c) If the answer to (b) is no, is the feature really so important that
it's worth adding extra overhead to the parse for all users in order to
benefit the (presumably tiny) minority who might actually be trying to
build perf at -O0?

p.