From: Phil Blundell <pb@pbcl.net>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [master][dora][PATCH 1/2] perf: disallow debug optimization.
Date: Thu, 21 Nov 2013 21:22:04 +0000 [thread overview]
Message-ID: <1385068924.4213.19.camel@x121e.pbcl.net> (raw)
In-Reply-To: <1385049423.23724.173.camel@phil-desktop.brightsign>
On Thu, 2013-11-21 at 15:57 +0000, Phil Blundell wrote:
> 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?
I suppose the other question is: why exactly does perf fail to build at
-O0, and can we just patch it so that it works rather than forcing
optimisation on? Even if it can't be fixed, it would be good for the
commit message associated with any workaround to explain what the
problem is.
p.
next prev parent reply other threads:[~2013-11-21 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 7:33 [master][dora][PATCH 0/2] Few perf fixes Mark Hatle
2013-11-21 7:33 ` [master][dora][PATCH 1/2] perf: disallow debug optimization Mark Hatle
2013-11-21 14:25 ` Phil Blundell
2013-11-21 14:35 ` Richard Purdie
2013-11-21 14:48 ` Mark Hatle
2013-11-21 17:43 ` Phil Blundell
2013-11-21 14:47 ` Mark Hatle
2013-11-21 15:57 ` Phil Blundell
2013-11-21 21:22 ` Phil Blundell [this message]
2013-11-21 7:33 ` [master][dora][PATCH 2/2] perf: Disable -Werror flag Mark Hatle
2013-11-21 15:26 ` Konrad Scherer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1385068924.4213.19.camel@x121e.pbcl.net \
--to=pb@pbcl.net \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox