From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: Please include const-sections into linux-next
Date: Wed, 19 Oct 2011 10:54:23 -0500 [thread overview]
Message-ID: <1319039663.3034.18.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <0e9ef9174a0089187fde0b3d084672ad.squirrel@www.firstfloor.org>
On Sun, 2011-10-16 at 23:57 +0200, Andi Kleen wrote:
> vate email?
> >
> > OK, so after fixing up that one, the next failure is:
> >
> > drivers/net/fealnx.c:95: error: version causes a section type conflict
> > drivers/net/fealnx.c:1944: error: fealnx_pci_tbl causes a section type
> > conflict
>
> Hmm, this is weird (just like the other error)
> I wonder if the pa-risc tool chain has some general problems with sections
>
> On a successful build with the same config could you send me the output of
>
> make drivers/net/fealnx.s
> and
> make drivers/net/fealnx.i
> in the same config privately? From that I can see if there's something else
> in init.rodata that does not match my i386 build.
Yes, I'll send under separate cover.
> One alternative to track it down would be to apply the attached
> patch to the gcc, then gcc would print it out.
I think the basic problem that excites the toolchain somehow is
sectional annotations. Can't we just dump them and do it all in a
linker script? Linker scripts seem to be much better tested.
James
next prev parent reply other threads:[~2011-10-19 15:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 23:38 Andi Kleen
2011-10-14 0:04 ` Stephen Rothwell
2011-10-14 22:26 ` James Bottomley
2011-10-15 22:38 ` [patch] parisc, iommu: add missing include for prefetchw() David Rientjes
2011-10-15 23:48 ` James Bottomley
2011-10-16 0:41 ` David Rientjes
2011-10-16 0:56 ` James Bottomley
2011-10-16 1:15 ` David Rientjes
2011-10-15 23:03 ` Please include const-sections into linux-next David Rientjes
2011-10-15 23:49 ` James Bottomley
2011-10-16 0:53 ` David Rientjes
2011-10-16 0:58 ` James Bottomley
2011-10-16 3:35 ` Andi Kleen
2011-10-16 21:03 ` James Bottomley
2011-10-16 21:57 ` Andi Kleen
2011-10-19 15:54 ` James Bottomley [this message]
2011-10-19 16:15 ` Andi Kleen
2011-10-19 16:21 ` James Bottomley
2011-10-19 16:33 ` Andi Kleen
2011-10-19 18:55 ` James Bottomley
2011-10-19 19:05 ` Andi Kleen
2011-10-19 20:04 ` James Bottomley
2011-10-19 20:06 ` James Bottomley
2011-10-19 20:11 ` Andi Kleen
2011-10-19 20:14 ` James Bottomley
2011-10-19 21:24 ` Andi Kleen
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=1319039663.3034.18.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=andi@firstfloor.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®