Uninitialized variable warnings

[Jeffrey A Law]

  In message < 199903152127.VAA32106@phal.cygnus.co.uk >you write:
  > > I've added some more test cases to the testsuite.  I will be sending
  > > patches for the real bugs and the documented failures shortly.  If
  > > people could look at the questionable cases, I'd appreciate it.
  > > 
  > > The list:
  > > 
  > > -- possibly real bugs --
  > > file		function		variable
  > ...
  > > regmove.c	fixup_match_1		dst_note
  > 
  > No bug here.  The use of dst_note depends on (success != 0) .  Success is
  > initialized to 0, and only set to 1 in a code path where dest_note is
  > initialized.
Agreed.  This _may_ be an example of the cases we may be able to detect via
control dependence analysis.  I've got no problem if someone initializes
dst_note to NULL_RTX.

  > > regmove.c	fixup_match_1		insn_const
  > 
  > No bug here, either.  Early in the function, either code is set to NOTE,
  > or insn_const is set, or the function returns early.
  > insn_const is never used if code is NOTE.
Similarly.  Control dependence analysis may allow us to tackle this one
someday.  Initializing insn_const to NULL_RTX seems reasonable to me.

Can someone work with Joern to deal with the reload issues?

jeff