This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
In message <199904090952.CAA06112@netcom8.netcom.com>you write: > > gcc emits many warnings about uninitialized variables while bootstrapping. > This patch fixes a few of them - I'll try to keep working on it. > Compiler appears to be successfully bootstrapping on i386-linux (so far) > with these changes. > > Fri Apr 9 Fri Apr 9 1999 Toshiyasu Morita (tm@netcom.com) > > fold-const.c (make_range): Ensure variables initialized. > (fold): Same. > function.c (fixup_var_refs_insns): Same. > (instantiate_virtual_regs_1): Same. > optabs.c (expand_binop): Same. > stmt.c (expand_end_case): Same. Please try to write correct ChangeLog entries. It is a waste of my time to have to fix them. The proper format is: <tab>* filename (function or variable): What changed. Also note, that simply initializing the variables to zero isn't necessarily the way to fix these problems. You need to actually analyze the cases to decide if zero initialization is actually correct (it may not be). I believe for the cases you submitted zero initialization is correct, but I wanted to make sure you are not just assuming zero initialization is the right thing to do. I've fixed up the ChangeLog entry and installed your patch. Also note, you may need to get an updated copyright assignment on file if you intend to submit additional patches (I can't verify your assignment at the moment due to problems at the FSF). Thanks, jeff
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |