From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: use local label prefixes for __reg_num symbols
Date: Thu, 28 Jan 2016 15:04:41 +0000 [thread overview]
Message-ID: <20160128150441.GF775@arm.com> (raw)
In-Reply-To: <1453917687-2494-1-git-send-email-ard.biesheuvel@linaro.org>
On Wed, Jan 27, 2016 at 07:01:27PM +0100, Ard Biesheuvel wrote:
> The __reg_num_xNN symbols that are used to implement the msr_s and
> mrs_s macros are recorded in the ELF metadata of each object file.
> This is not a problem in terms of code size, but it does clobber
> the output of tools like readelf, i.e.,
>
> $ readelf -a vmlinux |grep __reg_num_x | wc -l
> 50976
>
> So let's use symbols with the .L prefix, these are strictly local,
> and don't end up in the object files.
>
> $ readelf -a vmlinux |grep __reg_num_x | wc -l
> 0
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> arch/arm64/include/asm/sysreg.h | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
Looks harmless enough:
Acked-by: Will Deacon <will.deacon@arm.com>
Will
prev parent reply other threads:[~2016-01-28 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 18:01 [PATCH] arm64: use local label prefixes for __reg_num symbols Ard Biesheuvel
2016-01-27 18:02 ` Ard Biesheuvel
2016-01-28 15:04 ` Will Deacon [this message]
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=20160128150441.GF775@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).