public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, Anders Kaseorg <andersk@mit.edu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Lots of unexpected non-allocatable section warnings
Date: Sun, 03 May 2009 20:18:24 +0200	[thread overview]
Message-ID: <m21vr6124v.fsf@igel.home> (raw)
In-Reply-To: <20090503124848.276b437f@hyperion.delvare> (Jean Delvare's message of "Sun, 3 May 2009 12:48:48 +0200")

Jean Delvare <khali@linux-fr.org> writes:

> Hi Sam,
>
> Thanks for your swift answer.
>
> On Sun, 3 May 2009 12:30:10 +0200, Sam Ravnborg wrote:
>> On Sun, May 03, 2009 at 11:05:17AM +0200, Jean Delvare wrote:
>> > Hi Anders, Sam,
>> > 
>> > After your fix "kbuild, modpost: Check the section flags, to catch
>> > missing ax/aw", I get a lot of warnings like the following during
>> > modpost on x86-64:
>> > 
>> > WARNING: arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.o (.comment.SUSE.OPTs): 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.
>> > 
>> > Apparently there's one such warning for every module on my system, that
>> > is, 907. That's a lot, and pretty annoying. How do I solve this? I don't
>> > know much about assembly.
>> 
>> Cannot reproduce here..
>
> Given the name of the section, I presume it is somewhat SUSE-specific.
> I'm running openSUSE 11.1.

The section is created by the SUSE compiler and contains a summary of
the options used for compiling the file.  It should be treated like a
.comment section.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

      parent reply	other threads:[~2009-05-03 18:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03  9:05 Lots of unexpected non-allocatable section warnings Jean Delvare
2009-05-03 10:30 ` Sam Ravnborg
2009-05-03 10:42   ` Stephen Rothwell
2009-05-03 18:07     ` [PATCH] modpost: more complete endianness fixing Anders Kaseorg
2009-05-03 19:48       ` Sam Ravnborg
2009-05-04  8:00         ` Jean Delvare
2009-05-03 10:48   ` Lots of unexpected non-allocatable section warnings Jean Delvare
2009-05-03 18:03     ` Sam Ravnborg
2009-05-03 20:29       ` Sam Ravnborg
2009-05-04  7:58         ` Jean Delvare
2009-05-04  9:51           ` Sam Ravnborg
2009-05-04  8:28         ` 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
2009-05-03 18:18     ` Andreas Schwab [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=m21vr6124v.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=andersk@mit.edu \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --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