[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090623192304.GA23124@uranus.ravnborg.org>
Date: Tue, 23 Jun 2009 21:23:04 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Kyle McMartin <kyle@...artin.ca>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linus <torvalds@...ux-foundation.org>,
James Simmons <jsimmons@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
Krzysztof Helt <krzysztof.h1@...zta.fm>,
Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com>,
Andrew Morton <akpm@...ux-foundation.org>,
ppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH v2] fbdev: work around old compiler bug
On Tue, Jun 23, 2009 at 12:45:05PM -0400, Kyle McMartin wrote:
> On Tue, Jun 23, 2009 at 03:44:28PM +1000, Stephen Rothwell wrote:
> > When building with a 4.1.x compiler on powerpc64 (at least) we get
> > this error:
> >
> > drivers/video/logo/logo_linux_mono.c:81: error: logo_linux_mono causes a section type conflict
> >
> > This was introduced by commit ae52bb2384f721562f15f719de1acb8e934733cb
> > ("fbdev: move logo externs to header file"). This is a partial revert
> > of that commit sufficient to not hit the compiler bug.
> >
>
> We're seeing similar issues with 4.3 on parisc (the case I saw today was
> in fs/nfs/nfsroot.c...) Any ideas on the actual culprit or is it just
> gcc being unfriendly?
Al analysed this some time ago.
When we say something is const then _sometimes_ gcc annotate the
section as const(*) - sometimes not.
So if we have two variables/functions annotated __*const and
gcc decides to annotate the section const only in one case
we get a section type conflict.
(*) it is named something else I do not recall at the moment
in linker language.
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists