From: Nick Clifton <nickc@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Michael Petlan <mpetlan@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
kernel-team@lge.com
Subject: Re: [RFC] perf tools: Filter out hidden symbols from labels
Date: Wed, 16 Jan 2019 15:47:50 +0000 [thread overview]
Message-ID: <db34cf8a-d929-ffe1-91a5-ed3da0c6df86@redhat.com> (raw)
In-Reply-To: <20190116133117.GA2243@kernel.org>
Hi Arnaldo,
>> Unfortunately the annobin notes will probably not be very helpful as they
>> only record a minor subset of the typical gcc command line options.
>> (Specifically: -O, -g, -D_FORTIFY_SOURCE, -D_GLIBCXX_ASSERTIONS,
>> -fcf-protection, -fpic (and variants), -fshort-enum, -fstack-clash-protection,
>> -fstack-protector, -mstackrealign, -fexceptions).
>
> Humm, is -fno-omit-frame-pointer there by any chance? :-)
Not at the moment, although it could be added. All of the options
mentioned in the above list are recorded because they have an impact
on the security hardening of the binary. Other options are ignored
because, at least for now, they have no security implications.
Cheers
Nick
next prev parent reply other threads:[~2019-01-16 15:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 13:53 Jiri Olsa
2019-01-15 16:13 ` Nick Clifton
2019-01-15 16:35 ` Arnaldo Carvalho de Melo
2019-01-16 4:37 ` Namhyung Kim
2019-01-16 11:38 ` Nick Clifton
2019-01-16 13:31 ` Arnaldo Carvalho de Melo
2019-01-16 15:47 ` Nick Clifton [this message]
2019-01-16 16:04 ` Arnaldo Carvalho de Melo
2019-01-17 10:25 ` Nick Clifton
2019-01-17 13:26 ` Arnaldo Carvalho de Melo
2019-01-15 17:38 ` [RFCv2] " Jiri Olsa
2019-01-28 13:35 ` [PATCH] " Jiri Olsa
2019-01-29 9:07 ` Arnaldo Carvalho de Melo
2019-01-29 11:25 ` Nick Clifton
2019-01-29 11:39 ` Arnaldo Carvalho de Melo
2019-01-29 12:57 ` Nick Clifton
2019-01-29 12:58 ` Nick Clifton
2019-02-04 14:45 ` Arnaldo Carvalho de Melo
2019-02-09 12:22 ` [tip:perf/urgent] perf symbols: " tip-bot for Jiri Olsa
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=db34cf8a-d929-ffe1-91a5-ed3da0c6df86@redhat.com \
--to=nickc@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.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
all inboxes | Powered by JetHome®