Re: [git patches 1/2] warnings: attack valid cases spotted by warnings

[Roland Dreier <rdreier@cisco.com>]

 >     drivers/infiniband/hw/mthca/mthca_qp: kill uninit'd var warning
 >     
 >     drivers/infiniband/hw/mthca/mthca_qp.c: In function
 >       ‘mthca_tavor_post_send’:
 >     drivers/infiniband/hw/mthca/mthca_qp.c:1594: warning: ‘f0’ may be used
 >       uninitialized in this function
 >     drivers/infiniband/hw/mthca/mthca_qp.c: In function
 >       ‘mthca_arbel_post_send’:
 >     drivers/infiniband/hw/mthca/mthca_qp.c:1949: warning: ‘f0’ may be used
 >       uninitialized in this function
 >     
 >     Initializing 'f0' is not strictly necessary in either case, AFAICS.
 >     
 >     I was considering use of uninitialized_var(), but looking at the
 >     complex flow of control in each function, I feel it is wiser and
 >     safer to simply zero the var and be certain of ourselves.
 >     
 >     Signed-off-by: Jeff Garzik <jeff@garzik.org>

I don't really like this.  These functions are in the hottest, most
latency-sensitive code path of this driver, which is used by people
who care about nanoseconds.  I'm quite confident that the code is
correct as written, and it really feels wrong to me to add bloat to
the fastpath just to cover up a shortcoming of gcc.

And I don't like using uninitialized_var() here for a similar
reason... the functions are complex and I would prefer to avoid hiding
future bugs that may creep in.  In fact adding the initialization to 0
has a similar effect, since it shuts up the compiler even if the logic
in the function gets screwed up.

On the other hand I definitely sympathize with the desire to have a
warning-free build so that real warnings are more visible.  I guess I
could live with the uninitialized_var() patch, although I would feel a
little sad.

 - R.