Re: Patch for various warnings in gcc

[Michael Matz <matz at suse dot de>]

Hi,

On Thu, 8 Aug 2002, Kaveh R. Ghazi wrote:

>  > Personally I agree with Dale that 'int a = a;' is too obscure a way of
>  > silencing this warning.  If we must have a way to disable it without
>  > generating extra code, let us create __attribute__ ((initialized))
>  > which states explicitly what is going on.
>
> The attribute would be more readable but it would still suffer from
> the non-determinism, right?
>
> I favor my original '= 0' patch.  Michael is that ok?

I don't like this at all (to clutter the code when I know, it's
unnecessary).  I know, that there is no non-determinism currently, and
it's unlikely to creep in (after all there are heaps of other consistency
checks in the allocator), but if nobody teaches me attributes, and there's
opposition against a=a things (whose existance I completely understand),
then yes, it's Ok enough with me, if a comment is added, that the
assignment is just there to silence a warning.


Ciao,
Michael.