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 14:25:45 +0000 [thread overview]
Message-ID: <1385043945.23724.158.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <1385019198-24458-2-git-send-email-mark.hatle@windriver.com>
On Thu, 2013-11-21 at 01:33 -0600, Mark Hatle wrote:
> +def get_optimization(d):
> + selected_optimization = d.getVar("SELECTED_OPTIMIZATION", True)
> + if base_contains("SELECTED_OPTIMIZATION", "-O0", "x", "", d) == "x":
> + bb.note("eglibc can't be built with -O0, -O2 will be used instead.")
Although the text of that warning is correct, users might find the
reference to eglibc slightly confusing if it's perf that they're trying
to build.
Also, as I mentioned in a different thread not all that long ago when
someone submitted a similar patch for gcc-runtime, the proliferation of
parse-time python functions to bash SELECTED_OPTIMIZATION around doesn't
seem like all that good a thing: this will cause extra overhead for
everyone, even those who are not using -O0 and have no interest in perf.
And, finally, it remains slightly unclear to me that this is really a
problem that the metadata needs to be solving. I haven't seen any
particularly convincing explanation of why this can't or shouldn't just
be fixed in the distro configuration.
p.
next prev parent reply other threads:[~2013-11-21 14:26 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 [this message]
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
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=1385043945.23724.158.camel@phil-desktop.brightsign \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.