From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Eliminate the .eh_frame sections from the aarch64 vmlinux and kernel modules
Date: Fri, 22 Jan 2016 15:02:56 +0000 [thread overview]
Message-ID: <20160122150256.GC11645@leverpostej> (raw)
In-Reply-To: <56A2400D.5080707@redhat.com>
On Fri, Jan 22, 2016 at 09:43:25AM -0500, William Cohen wrote:
> On 01/22/2016 02:41 AM, Ard Biesheuvel wrote:
> > On 22 January 2016 at 04:56, William Cohen <wcohen@redhat.com> wrote:
> >> By default the aarch64 gcc generates .eh_frame sections. Unlike
> >> .debug_frame sections, the .eh_frame sections are loaded into memory
> >> when the associated code is loaded. On an example kernel being built
> >> with this default the .eh_frame section in vmlinux used an extra 1.7MB
> >> of memory. The x86 disables the creation of the .eh_frame section.
> >> The aarch64 should probably do the same to save some memory.
> >>
> >
> > With my GCC-4.9.3 Linaro toolchain, I am not getting .eh_frame
> > sections only .debug_frame sections. The patch still makes sense imo,
> > but it appears to be redundant in some cases, and it would be useful
> > to figure out why. Which toolchain have you tested this with?
>
> Hi,
>
> I have observed the .eh_frame being generated with gcc-5.3.1 that is in Fedora 23.
FWIW, I do not see this with the Linaro 15.08 GCC 5.1.1.
It would be interesting to know if that's something that changed
upstream between 5.1.x and 5.3.x or if that's a Fedora-specific
configuration option, but either way the patch seems reasonable.
Thanks,
Mark.
next prev parent reply other threads:[~2016-01-22 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 3:56 [PATCH] Eliminate the .eh_frame sections from the aarch64 vmlinux and kernel modules William Cohen
2016-01-22 7:41 ` Ard Biesheuvel
2016-01-22 14:43 ` William Cohen
2016-01-22 15:02 ` Mark Rutland [this message]
2016-01-22 15:36 ` William Cohen
2016-01-22 17:02 ` Mark Rutland
2016-01-22 19:03 ` William Cohen
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=20160122150256.GC11645@leverpostej \
--to=mark.rutland@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).