[U-Boot] compile errors with gcc-4.5.1 on OXC and RMU boards

[Kumar Gala]

On Dec 13, 2010, at 10:15 AM, Wolfgang Denk wrote:

> Dear Kumar Gala,
> 
> In message <E7F59234-4A15-4B96-B2FB-0FB3EEDC58A5 at kernel.crashing.org> you wrote:
>> 
>>> Or has the rule officially been dropped that the "#if" in the C
>>> prepro use the same shortcut logic as the "if" in C?
>> 
>> I'm being told that not reporting this as an error is a bug in previous
>> gcc's not the new one.  There isn't anything in the C specs about early
>> out handling from what I can tell.
> 
> But there is nothing in the specs that states that always all
> conditions need to be evaluated or at least checked if they can be
> evaluated reasonably.  To me, the new behaviour makes no sense -
> neither logically not performance-wise.
> 
> I am aware that common sense and gcc behaviour is not always in the
> same pot, but I consider this to be a change to the worse.
> 
> Can you point to some commit / bugzilla entry / posting that contains
> an explanation or rationale for this change?

Hopefully, Nathan can provide some input on this.

- k