public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap3evm: Clean-up EVM detection code.
Date: Thu, 02 Dec 2010 13:33:47 +0100	[thread overview]
Message-ID: <4CF7922B.3020504@free.fr> (raw)
In-Reply-To: <20101202120141.30416EA6600@gemini.denx.de>

Le 02/12/2010 13:01, Wolfgang Denk a ?crit :
> Dear Albert ARIBAUD,
>
> In message<4CF7896B.5090007@free.fr>  you wrote:
>>
>> Note that initialization should be unnecessary if the static variable is
>> int rather than u8.
>
> It should ALWAYS be not necessary.

I understand your point re: the linker warning, i.e. initializing should 
never be done to just get rid of a warning.

> Otherwise we have a bug, and that bug needs to be fixed rather than
> papered over.

Yes, there is a bug whereby an u8 BSS variable causes a linker warning, 
and I believe this bug to be with the linker -- I'm working on getting a 
minimal example of it so that I could completely verify that the warning 
does not affect the semantics of the code generated.

Now, on an unrelated note, omap3_emv's code arbitrarily uses an u8 where 
an int (or enum) would be more appropriate, and this should be changed 
not because it removes a linker warning, but because the u8 choice is 
arbitrary and at best as effective as using an int, at worst suboptimal 
to that.

> Best regards,
>
> Wolfgang Denk

Amicalement,
-- 
Albert.

  reply	other threads:[~2010-12-02 12:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 11:20 [U-Boot] [PATCH] omap3evm: Clean-up EVM detection code Sanjeev Premi
2010-12-02 11:37 ` Wolfgang Denk
2010-12-02 11:56   ` Albert ARIBAUD
2010-12-02 12:01     ` Wolfgang Denk
2010-12-02 12:33       ` Albert ARIBAUD [this message]
2010-12-02 13:58         ` Wolfgang Denk
2010-12-02 16:23           ` Albert ARIBAUD
2010-12-02 18:51             ` Wolfgang Denk
2010-12-02 19:32               ` Albert ARIBAUD
2010-12-02 13:30   ` Premi, Sanjeev

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=4CF7922B.3020504@free.fr \
    --to=albert.aribaud@free.fr \
    --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