[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87wsyg2wbd.wl%peter@chubb.wattle.id.au>
Date: Thu, 07 Jun 2007 15:00:22 +1000
From: Peter Chubb <peter@...bb.wattle.id.au>
To: Russ Anderson <rja@....com>
Cc: tony.luck@...el.com (Luck Tony),
prarit@...hat.com (Prarit Bhargava),
clameter@....com (Christoph Lameter),
randy.dunlap@...cle.com (Randy Dunlap),
dgc@....com (David Chinner),
akpm@...ux-foundation.org (Andrew Morton),
linux-kernel@...r.kernel.org (lkml), linux-ia64@...r.kernel.org,
sam@...nborg.org (Sam Ravnborg)
Subject: Re: linux-ia64 build warning messages
>>>>> "Russ" == Russ Anderson <rja@....com> writes:
Russ> Tony Luck wrote:
>> > I used the sn2_defconfig in the tree :)
>>
>> So there is something odd happening. Russ complained that he was
>> still seeing several errors from the sn2_defconfig build too when I
>> posted the "last fix" to Len. But I don't see them when I build.
Russ> An additional data point. I have a copy of Tony's test tree
Russ> pulled down on March 30th that builds without the warning
Russ> messages. The copy of Tony's test tree pulled down on May 22nd
Russ> does have warning messages. I'm building both with the same
Russ> compiler (etc). I'm fairly certain a tree I pulled down in
Russ> April built without warnings. I've since blown away that tree.
Change request 85bd2fddd68e757da8e1af98f857f61a3c9ce647 introduced
section-mismatch checking for vmlinux, which caused all these warnings
to become visible.
It looks as if gcc can create references from .sdata to .init.sdata
depending on what optimisations it chooses to do. Ideally we could
teach gcc to put its constants in the same section they reference.
But I'm no gcc guru. The alternative is to get modpost to ignore such
references, at the cost of perhaps missing a real problem somewhere.
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia
-
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