[Bug c++/30680] Spurious might be used uninitialized warning in STL use.

2009-03-08 Thread dick dot dunbar at gmail dot com
--- Comment #5 from dick dot dunbar at gmail dot com 2009-03-08 17:59 --- Subject: Spurious 2 years without a test case? The very first post provides a test case. All boost users are affected by this bug. Bugzilla from gcc-bugzi...@gcc.gnu.org wrote: --- Comment #4 from

[Bug c++/30680] Spurious might be used uninitialized warning in STL use.

2009-03-08 Thread steven at gcc dot gnu dot org
--- Comment #6 from steven at gcc dot gnu dot org 2009-03-08 18:08 --- Re. comment #5. Two years without a test case that allows us to reproduce the bug. REPRODUCE the bug. Is that too hard for you to understand? If we can't reproduce the bug, we can't diagnose the problem and fix

[Bug c++/30680] Spurious might be used uninitialized warning in STL use.

2009-02-07 Thread manu at gcc dot gnu dot org
--- Comment #4 from manu at gcc dot gnu dot org 2009-02-07 16:30 --- Two years without testcase. I cannot reproduce. Probably a duplicate. Marked as INVALID. Please, reopen if you have a reproducible testcase obtained following http://gcc.gnu.org/bugs.html#report -- manu at gcc dot

[Bug c++/30680] Spurious might be used uninitialized warning in STL use.

2008-09-30 Thread pdemarco at ppg dot com
--- Comment #3 from pdemarco at ppg dot com 2008-09-30 20:00 --- (In reply to comment #2) maybe the same bug to 22207? yeah, probably the same as bug 22207, but that one is only fixed on 4.0.0 We need a fix on 3.x.x -- pdemarco at ppg dot com changed: What|Removed

[Bug c++/30680] Spurious might be used uninitialized warning in STL use.

2007-09-10 Thread jsli at yahoo dot com
--- Comment #2 from jsli at yahoo dot com 2007-09-10 09:56 --- maybe the same bug to 22207? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30680

[Bug c++/30680] Spurious might be used uninitialized warning in STL use.

2007-08-21 Thread manu at gcc dot gnu dot org
--- Comment #1 from manu at gcc dot gnu dot org 2007-08-21 09:00 --- Hi, could you attach a preprocessed testcase (*.i) generated by adding -save-temps ? The minimal the testcase, the better. Thanks. -- manu at gcc dot gnu dot org changed: What|Removed