[Bug middle-end/44307] warning: may be used uninitialized in this function often building gcc

2010-06-04 Thread jay dot krell at cornell dot edu
--- Comment #7 from jay dot krell at cornell dot edu 2010-06-04 16:30 --- I mean -Wuninitialized. -Werror is already omitted. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44307

[Bug middle-end/44307] warning: may be used uninitialized in this function often building gcc

2010-06-04 Thread manu at gcc dot gnu dot org
--- Comment #6 from manu at gcc dot gnu dot org 2010-06-04 16:22 --- (In reply to comment #5) > Then don't use when I -disable-bootstrap.. > Do you mean that -Werror is used when you disable-bootstrap? If so, I think that is a bug. Or you mean to not use warnings? I think that would be

[Bug middle-end/44307] warning: may be used uninitialized in this function often building gcc

2010-06-04 Thread jay dot krell at cornell dot edu
--- Comment #5 from jay dot krell at cornell dot edu 2010-06-04 16:20 --- Then don't use when I -disable-bootstrap.. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44307

[Bug middle-end/44307] warning: may be used uninitialized in this function often building gcc

2010-06-04 Thread manu at gcc dot gnu dot org
--- Comment #4 from manu at gcc dot gnu dot org 2010-06-04 15:56 --- Hi Jay, -Wuninitialized is quite unreliable in old compilers and also we do not know what patches Apple applies to its copy of GCC. This is why -Werror is not used in the first stage of building GCC. We do not see thes

[Bug middle-end/44307] warning: may be used uninitialized in this function often building gcc

2010-05-28 Thread jsm28 at gcc dot gnu dot org
--- Comment #3 from jsm28 at gcc dot gnu dot org 2010-05-28 11:35 --- Stop using "c" as the component for bugs that are obviously not front-end bugs. In this case, you can see that none of the files mentioned are front-end files. -- jsm28 at gcc dot gnu dot org changed: