From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Sun, 21 Aug 2011 12:13:56 +0200 Subject: [U-Boot] [STATUS] ARM In-Reply-To: References: <4E4D8DB4.6030800@aribaud.net> <4E4E2F1C.6080300@ti.com> <4E4EA91B.2050007@googlemail.com> <4E4F9692.8020502@aribaud.net> <4E4FD3A0.7060309@aribaud.net> <4E50BE5E.1080909@aribaud.net> Message-ID: <4E50DA64.90804@aribaud.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Aneesh, Le 21/08/2011 10:56, V, Aneesh a ?crit : >> This indeed fixes it. Strange that the warning is not emitted by your >> toolchain. > > Yes, that's indeed strange. Even with your tool-chain it should've emitted > more warnings. Many of those unsigned variables were assigned -1 in > elsewhere. That was also never reported. Actually I only gave one of those warnings. For a single build of omap4_panda, there was the following: clocks.c:274: warning: comparison is always true due to limited range of data type clocks.c:276: warning: comparison is always true due to limited range of data type clocks.c:278: warning: comparison is always true due to limited range of data type clocks.c:280: warning: comparison is always true due to limited range of data type clocks.c:282: warning: comparison is always true due to limited range of data type clocks.c:284: warning: comparison is always true due to limited range of data type But note that these are comparisons, not assignments. The semantics of ether operation might explain why one causes a warning and not the other. > br, > Aneesh Amicalement, -- Albert.