[Xen-devel] Re: Section conflicts with percpu variables

[Tejun Heo <tj@xxxxxxxxxx>]

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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel