From: Denys Vlasenko <vda.linux@googlemail.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
linux-arch@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 1/4] modpost: support objects with more than 64k sections
Date: Thu, 29 Jul 2010 02:13:26 +0200 [thread overview]
Message-ID: <201007290213.26738.vda.linux@googlemail.com> (raw)
In-Reply-To: <1280360876-2571-2-git-send-email-vda.linux@googlemail.com>
On Thursday 29 July 2010 01:47, Denys Vlasenko wrote:
> This patch makes modpost able to process object files with more than
> 64k sections. Needed for huge kernel builds (allyesconfig, for example)
> with -ffunction-sections.
>
> Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
> Signed-off-by: Anders Kaseorg <andersk@mit.edu>
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Cc: Andi Kleen <andi@firstfloor.org>
I forgot to mention in the changelog that 64k sections handling
is covered, for example, by this document:
"IA-64 gABI Proposal 74: Section Indexes"
http://www.codesourcery.com/public/cxx-abi/abi/prop-74-sindex.html
--
vda
next prev parent reply other threads:[~2010-07-29 0:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 23:47 [PATCH 0/4] function/data-sections Denys Vlasenko
2010-07-28 23:47 ` [PATCH 1/4] modpost: support objects with more than 64k sections Denys Vlasenko
2010-07-29 0:13 ` Denys Vlasenko [this message]
2010-07-28 23:47 ` [PATCH 2/4] module linker script: coalesce function and data sections Denys Vlasenko
2010-07-29 0:25 ` David Howells
2010-07-29 1:24 ` Denys Vlasenko
2010-07-29 9:09 ` David Howells
2010-08-03 13:47 ` Michal Marek
2010-08-06 2:18 ` Denys Vlasenko
2010-07-28 23:47 ` [PATCH 3/4] kernel linker stripts: accomodate " Denys Vlasenko
2010-07-28 23:47 ` [PATCH 4/4] boot " Denys Vlasenko
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=201007290213.26738.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.