From: Sam Ravnborg <sam@ravnborg.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
rdunlap@xenotime.net, akpm@osdl.org, jgarzik@pobox.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] [2.6.17-rc6] Section mismatch in drivers/net/ne.o during modpost
Date: Tue, 13 Jun 2006 22:38:28 +0200 [thread overview]
Message-ID: <20060613203828.GA26690@mars.ravnborg.org> (raw)
In-Reply-To: <10735.1150176929@kao2.melbourne.sgi.com>
> Probably over enthusiastic gcc inlining. gcc 4 will inline functions
> that are not declared as inline. That is not so bad, except that some
> versions of gcc will ignore a mismatch in function attributes and
> inline a __init function into normal text, generating additional
> section mismatches.
When using -ffunction-sections (or similar) then we ask gcc to put each
function in separate sections. In this case it is OK to mix sections.
But I agree, gcc should not mix user specified sections.
> For a specific example, see
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=113824309203482&w=2
That's a good example - thanks!
Sam
next prev parent reply other threads:[~2006-06-13 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 0:51 [PATCH] [2.6.17-rc6] Section mismatch in drivers/net/ne.o during modpost Mikael Pettersson
2006-06-11 10:25 ` Jan Engelhardt
2006-06-13 5:35 ` Keith Owens
2006-06-13 15:11 ` Randy.Dunlap
2006-06-13 20:38 ` Sam Ravnborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-11 14:37 Mikael Pettersson
2006-06-11 21:54 ` Sam Ravnborg
2006-06-10 12:11 Mikael Pettersson
2006-06-10 19:13 ` [PATCH] " Randy.Dunlap
2006-06-10 20:38 ` Sam Ravnborg
2006-06-11 10:23 ` Jan Engelhardt
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=20060613203828.GA26690@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).