From: Philip Kranz <philip.kranz@googlemail.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Philip Kranz <philip.kranz@googlemail.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Sebastian Wankerl <sisewank@cip.cs.fau.de>,
linux-kernel@vger.kernel.org,
i4passt@lists.informatik.uni-erlangen.de,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH] Add non-zero module sections to sysfs
Date: Mon, 8 Apr 2013 13:55:56 +0200 [thread overview]
Message-ID: <20130408115556.GB3561@yoda.lan> (raw)
In-Reply-To: <878v4tbqve.fsf@rustcorp.com.au>
On Mon, Apr 08, 2013 at 01:44:45PM +0930, Rusty Russell wrote:
> Philip Kranz <philip.kranz@googlemail.com> writes:
> > I am not able to produce an object file with duplicate section names
> > using gcc on x86. Even with -ffunction-sections, every section gets a
> > unique name. Is this architecture-specific behaviour of gcc?
>
> Good point. ld -r will collapse them into the same section (since gcc
> produces them they have to have the same section attributes).
>
> You can do it with --unique, but no arch uses that. PARISC has a
> platform-specific toolchain hack which does that for .text sections.
> (Thanks to Alan Modra for that clue...)
So that problem is indeed platform-specific. If it is safe to assume
that kernel modules don't have duplicate section names (except on
PARISC), it would make sense to simply move the check for empty sections
to arch/parisc as you suggested.
James, what do you think about that?
Greetings,
Philip
next prev parent reply other threads:[~2013-04-08 11:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1364994499-23708-1-git-send-email-sisewank@cip.cs.fau.de>
[not found] ` <87mwtf3ya1.fsf@rustcorp.com.au>
[not found] ` <515D4A7F.5070102@cip.cs.fau.de>
2013-04-05 4:00 ` [PATCH] Add non-zero module sections to sysfs Rusty Russell
2013-04-05 9:40 ` Sebastian Wankerl
2013-04-05 10:07 ` James Bottomley
2013-04-06 4:52 ` Rusty Russell
2013-04-06 10:52 ` James Bottomley
2013-04-06 15:16 ` John David Anglin
2013-04-07 1:22 ` James Bottomley
2013-04-07 1:45 ` John David Anglin
2013-04-06 10:40 ` Philip Kranz
2013-04-08 4:14 ` Rusty Russell
2013-04-08 11:55 ` Philip Kranz [this message]
2013-04-11 14:11 ` Philip Kranz
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=20130408115556.GB3561@yoda.lan \
--to=philip.kranz@googlemail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=i4passt@lists.informatik.uni-erlangen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sisewank@cip.cs.fau.de \
/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