public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] ARM
Date: Sun, 21 Aug 2011 12:13:56 +0200	[thread overview]
Message-ID: <4E50DA64.90804@aribaud.net> (raw)
In-Reply-To: <CAM=4YERmBNVgM2wRHyCKCqkXKWV8Ja667jFg0N1-Fu9nHk9Szw@mail.gmail.com>

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.

  reply	other threads:[~2011-08-21 10:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 22:09 [U-Boot] [STATUS] ARM Albert ARIBAUD
2011-08-19  9:38 ` Aneesh V
2011-08-19 18:19   ` Dirk Behme
2011-08-20 11:12     ` Albert ARIBAUD
2011-08-20 15:32       ` Albert ARIBAUD
2011-08-21  7:11         ` Dirk Behme
2011-08-21  7:22           ` Albert ARIBAUD
2011-08-23  2:02             ` V, Aneesh
2011-08-21  7:46         ` Dirk Behme
2011-08-21  7:54           ` V, Aneesh
2011-08-21  7:51         ` V, Aneesh
2011-08-21  8:14           ` Albert ARIBAUD
2011-08-21  8:56             ` V, Aneesh
2011-08-21 10:13               ` Albert ARIBAUD [this message]
2011-08-22  8:15       ` Simon Schwarz
2011-08-23 11:27         ` Michael Jones
2011-08-20 11:16 ` Marek Vasut
2011-08-20 11:44   ` Albert ARIBAUD
2011-08-20 12:24     ` Marek Vasut
2011-08-20 12:54       ` Albert ARIBAUD
2011-08-20 13:33         ` Marek Vasut
2011-08-20 18:50 ` [U-Boot] [STATUS] ARM (Tegra) Mike Frysinger
2011-08-30 15:20   ` Mike Frysinger
2011-08-30 15:34     ` Albert ARIBAUD
2011-08-30 15:57       ` Simon Glass
2011-08-30 16:27         ` Simon Glass
2011-08-30 16:31         ` Albert ARIBAUD
2011-08-30 16:36           ` Simon Glass
2011-08-30 16:39             ` Albert ARIBAUD
2011-08-30 16:45               ` Simon Glass
2011-08-21 10:17 ` [U-Boot] [STATUS] ARM Dirk Behme
2011-08-30 15:58 ` [U-Boot] [STATUS] ARM status as of 2011-08-30 Albert ARIBAUD
2011-08-30 19:08   ` Wolfgang Denk
2011-08-31 10:25     ` Albert ARIBAUD
2011-08-31 19:55       ` Wolfgang Denk

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=4E50DA64.90804@aribaud.net \
    --to=albert.u.boot@aribaud.net \
    --cc=u-boot@lists.denx.de \
    /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