* Re: Section conflicts with percpu variables [not found] <4CC8780C.8090401@goop.org> @ 2010-10-28 9:21 ` Tejun Heo 2010-10-29 14:16 ` Jeremy Fitzhardinge 0 siblings, 1 reply; 2+ messages in thread From: Tejun Heo @ 2010-10-28 9:21 UTC (permalink / raw) To: Jeremy Fitzhardinge Cc: Linux Kernel Mailing List, Xen-devel@lists.xensource.com, Teck Choon Giam On 10/27/2010 09:05 PM, Jeremy Fitzhardinge wrote: > Hi Tejun, > > I wonder if you could have a look at this. I have someone reporting > compilation failures when using the stock Centos 5 compiler: > > arch/x86/xen/mmu.c:163: error: __pcpu_scope_xen_cr3 causes a section type conflict > arch/x86/xen/mmu.c:164: error: __pcpu_scope_xen_current_cr3 causes a section type conflict > arch/x86/xen/mmu.c:163: error: __pcpu_unique_xen_cr3 causes a section type conflict > arch/x86/xen/mmu.c:164: error: __pcpu_unique_xen_current_cr3 causes a section type conflict > > Looking at mmu.i, I can't see why it is picking on these particular > per-cpu variables. Do you have any insight into this. Hmmm... me neither. section type conflict? Does it make any different if you move the definitions near the top of the file or use a different compiler version? Thanks. -- tejun ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Section conflicts with percpu variables 2010-10-28 9:21 ` Section conflicts with percpu variables Tejun Heo @ 2010-10-29 14:16 ` Jeremy Fitzhardinge 0 siblings, 0 replies; 2+ messages in thread From: Jeremy Fitzhardinge @ 2010-10-29 14:16 UTC (permalink / raw) To: Tejun Heo Cc: Linux Kernel Mailing List, Xen-devel@lists.xensource.com, Teck Choon Giam On 10/28/2010 02:21 AM, Tejun Heo wrote: > On 10/27/2010 09:05 PM, Jeremy Fitzhardinge wrote: >> Hi Tejun, >> >> I wonder if you could have a look at this. I have someone reporting >> compilation failures when using the stock Centos 5 compiler: >> >> arch/x86/xen/mmu.c:163: error: __pcpu_scope_xen_cr3 causes a section type conflict >> arch/x86/xen/mmu.c:164: error: __pcpu_scope_xen_current_cr3 causes a section type conflict >> arch/x86/xen/mmu.c:163: error: __pcpu_unique_xen_cr3 causes a section type conflict >> arch/x86/xen/mmu.c:164: error: __pcpu_unique_xen_current_cr3 causes a section type conflict >> >> Looking at mmu.i, I can't see why it is picking on these particular >> per-cpu variables. Do you have any insight into this. > Hmmm... me neither. section type conflict? Does it make any > different if you move the definitions near the top of the file or use > a different compiler version? This is the first report of this kind I've seen, so it mostly works. The compiler in question is the stock Centos 5 (.1?) compiler, so it would be nice to make sure it works as-is. I've seen section type conflicts with .discard before when discarding a function and a data type with the same section, which is why I added general support for .discard.* so they can all get their own sections. But that doesn't seem to be the case here. J ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-10-29 14:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <4CC8780C.8090401@goop.org>
2010-10-28 9:21 ` Section conflicts with percpu variables Tejun Heo
2010-10-29 14:16 ` Jeremy Fitzhardinge
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.