From: "Andi Kleen" <andi@firstfloor.org>
To: "James Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: "Andi Kleen" <andi@firstfloor.org>,
"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: Sun, 16 Oct 2011 23:57:25 +0200 [thread overview]
Message-ID: <0e9ef9174a0089187fde0b3d084672ad.squirrel@www.firstfloor.org> (raw)
In-Reply-To: <1318799006.2995.1.camel@dabdike.int.hansenpartnership.com>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
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.
One alternative to track it down would be to apply the attached
patch to the gcc, then gcc would print it out.
-Andi
[-- Attachment #2: section-conflict --]
[-- Type: application/octet-stream, Size: 1521 bytes --]
commit b74d9e7a4a76afe4fd769881525f89f89324be8c
Author: ak <ak@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Thu Jun 9 06:22:17 2011 +0000
better warning for section conflict
gcc/:
2011-06-08 Andi Kleen <ak@linux.intel.com>
* varasm.c (get_section): Print location of other conflict
for section conflicts.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@174836 138bc75d-0d04-0410-961f-82ee72b054a4
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 820bcbd..1c9fa02 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,5 +1,10 @@
2011-06-08 Andi Kleen <ak@linux.intel.com>
+ * varasm.c (get_section): Print location of other conflict
+ for section conflicts.
+
+2011-06-08 Andi Kleen <ak@linux.intel.com>
+
* config/i386/driver-i386.c (host_detect_local_cpu):
Add model 0x2d Intel CPU.
diff --git a/gcc/varasm.c b/gcc/varasm.c
index 3311c86..a0a0582 100644
--- a/gcc/varasm.c
+++ b/gcc/varasm.c
@@ -313,7 +313,11 @@ get_section (const char *name, unsigned int flags, tree decl)
if (decl == 0)
decl = sect->named.decl;
gcc_assert (decl);
- error ("%+D causes a section type conflict", decl);
+ error ("%+D causes a section type conflict with %D",
+ decl, sect->named.decl);
+ if (decl != sect->named.decl)
+ inform (DECL_SOURCE_LOCATION (sect->named.decl),
+ "%qD was declared here", sect->named.decl);
/* Make sure we don't error about one section multiple times. */
sect->common.flags |= SECTION_OVERRIDE;
}
next prev parent reply other threads:[~2011-10-16 21:57 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 [this message]
2011-10-19 15:54 ` James Bottomley
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=0e9ef9174a0089187fde0b3d084672ad.squirrel@www.firstfloor.org \
--to=andi@firstfloor.org \
--cc=James.Bottomley@HansenPartnership.com \
--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®