From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Martin Liška" <mliska@suse.cz>
Cc: 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: Wed, 20 May 2015 10:53:34 -0300 [thread overview]
Message-ID: <20150520135333.GE2955@kernel.org> (raw)
In-Reply-To: <555C8C41.1080608@suse.cz>
Em Wed, May 20, 2015 at 03:29:37PM +0200, Martin Liška escreveu:
> On 05/20/2015 03:17 PM, Arnaldo Carvalho de Melo wrote:
> >Em Wed, May 20, 2015 at 03:07:39PM +0200, Martin Liška escreveu:
> >>Currently, GCC optimizes -O6 same as -O3 level. Right optimize debugging
> >>experience is given by passing -Og to compiler.
> >Is this is this -Og available in old gcc versions? When was it
> >introduced? Do you know?
> GCC 4.8.0 is the first version capable of the option: https://gcc.gnu.org/gcc-4.8/changes.html.
> That can be problematic, which GCC version do you support in linux/perf?
So the rule has been: What are the kernel requirements for the
toolchain? tools/perf/ should build with that.
Looking at the kernel's README, that is...
-------------
COMPILING the kernel:
- Make sure you have at least gcc 3.2 available.
For more information, refer to Documentation/Changes.
--------------
The oldest toolchain I personally test from time to time is:
[acme@rhel5 ~]$ rpm -q gcc make binutils
gcc-4.1.2-55.el5
make-3.81-3.el5
binutils-2.17.50.0.6-26.el5
[acme@rhel5 ~]$
- Arnaldo
next prev parent reply other threads:[~2015-05-20 13:53 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 [this message]
2015-05-20 14:55 ` Ingo Molnar
2015-05-20 16:16 ` Martin Liška
2015-05-21 15:05 ` Arnaldo Carvalho de Melo
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=20150520135333.GE2955@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.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).