From: David Daney <ddaney@caviumnetworks.com>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Sam Ravnborg <sam@ravnborg.org>, Anders Kaseorg <andersk@mit.edu>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: Lots of unexpected non-allocatable section warnings
Date: Mon, 04 May 2009 08:26:02 -0700 [thread overview]
Message-ID: <49FF090A.3030505@caviumnetworks.com> (raw)
In-Reply-To: <20090504082816.GA25378@roarinelk.homelinux.net>
Manuel Lauss wrote:
> Hi Sam,
>
> On Sun, May 03, 2009 at 10:29:39PM +0200, Sam Ravnborg wrote:
>> This is due to the SUSE specific section as you expected.
>> We ignore sections named ".comment" but not ".comment" sections
>> with something appended to the name.
>
>
> On a related note, I see tons of the following warnings cross-building for
> MIPS:
>
> WARNING: init/mounts.o (.mdebug.abi32): unexpected non-allocatable section.
> Did you forget to use "ax"/"aw" in a .S file?
> Note that for example <linux/init.h> contains
> section definitions for use in .S files.
>
> WARNING: init/mounts.o (.pdr): unexpected non-allocatable section.
> Did you forget to use "ax"/"aw" in a .S file?
> Note that for example <linux/init.h> contains
> section definitions for use in .S files.
>
>
> I added ".pdr" and ".mdebug*" to the whitelist; the resulting kernels still
> work. (gcc-4.3.3, binutils-2.19.1)
>
I too think they are needed. Are you going to prepare a patch?
David Daney
prev parent reply other threads:[~2009-05-04 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090503110517.6d09bca2@hyperion.delvare>
[not found] ` <20090503103010.GA27978@uranus.ravnborg.org>
[not found] ` <20090503124848.276b437f@hyperion.delvare>
[not found] ` <20090503180332.GA31820@uranus.ravnborg.org>
[not found] ` <20090503202939.GA1237@uranus.ravnborg.org>
2009-05-04 8:28 ` Lots of unexpected non-allocatable section warnings Manuel Lauss
2009-05-04 9:49 ` Sam Ravnborg
2009-05-04 10:05 ` Manuel Lauss
2009-05-04 15:24 ` David Daney
2009-05-04 15:26 ` David Daney [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=49FF090A.3030505@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=andersk@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mano@roarinelk.homelinux.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox