From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Martin Liška" <mliska@suse.cz>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] perf: fix wrong DEBUG configuration
Date: Thu, 21 May 2015 12:05:36 -0300 [thread overview]
Message-ID: <20150521150536.GB13933@kernel.org> (raw)
In-Reply-To: <555CB373.7090007@suse.cz>
Em Wed, May 20, 2015 at 06:16:51PM +0200, Martin Liška escreveu:
> On 05/20/2015 04:55 PM, Ingo Molnar wrote:
> >* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> >>So the rule has been: What are the kernel requirements for the
> >>toolchain? tools/perf/ should build with that.
> >
> >So we could use -Og if it works, like Kbuild does it:
> >
> > KBUILD_CFLAGS += $(call cc-option,-mno-fp-ret-in-387)
> >
> >the 'cc-option' Make function does some magic of silently calling GCC
> >with that option and observing the result.
> >See:
> > scripts/Kbuild.include:cc-option = $(call try-run,\
> I am sorry, I did mistake in understanding of DEBUG variable.
> Following patch should be fixed, except missing auto-detection
> of -Og option.
>
> Unfortunately, following hunk does not work, no -Ox is added to CFLAGS?
>
> -- CFLAGS += -Og
> ++ CFLAGS += $(call cc-option,-Og,-O0)
I don't know if we have this cc-option, perhaps Ingo is suggesting we
get it in tools/build/? Or include scripts/Kbuild.include and then use
it?
I.e. we have checks to see if we can use, for instance
-fstack-protector-all, see tools/build/feature/Makefile, usong this
cc-option thing, importing it from Kbuild would solve the issue at
hand in a definitive way and in line with what we have been pursuing:
to make the tools/ build system be based on Kbuild.
- Arnaldo
next prev parent reply other threads:[~2015-05-21 15:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 13:41 [PATCH] perf: fix wrong DEBUG configuration Martin Liška
2015-05-19 14:04 ` Arnaldo Carvalho de Melo
2015-05-20 13:07 ` Martin Liška
2015-05-20 13:17 ` Arnaldo Carvalho de Melo
2015-05-20 13:29 ` Martin Liška
2015-05-20 13:53 ` Arnaldo Carvalho de Melo
2015-05-20 14:55 ` Ingo Molnar
2015-05-20 16:16 ` Martin Liška
2015-05-21 15:05 ` Arnaldo Carvalho de Melo [this message]
2015-05-22 7:02 ` Ingo Molnar
2015-05-22 13:50 ` Martin Liška
2015-05-25 8:04 ` Martin Liška
2015-05-25 10:47 ` Ingo Molnar
2015-05-25 11:04 ` Martin Liška
2015-05-25 11:09 ` Ingo Molnar
2015-05-25 11:12 ` Martin Liška
2015-05-25 13:52 ` Arnaldo Carvalho de Melo
2015-05-25 18:32 ` Ingo Molnar
2015-05-26 9:13 ` Martin Liška
2015-05-26 14:36 ` Arnaldo Carvalho de Melo
2015-05-26 15:22 ` Arnaldo Carvalho de Melo
2015-05-26 15:39 ` Martin Liška
2015-05-26 15:48 ` Martin Liška
2015-05-26 15:53 ` Arnaldo Carvalho de Melo
2015-05-27 16:51 ` [tip:perf/core] perf tools: Assign default value for some pointers tip-bot for Martin Liška
2015-05-27 16:51 ` [tip:perf/core] perf tools: Improve setting of gcc debug option tip-bot for Martin Liska
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=20150521150536.GB13933@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=mliska@suse.cz \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).