[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 Bug 2972 depends on bug 19808, which changed state. Bug 19808 Summary: miss a warning about uninitialized member usage in member initializer list in constructor https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19808 What|Removed

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Known to work|

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 --- Comment #24 from Richard Biener --- Author: rguenth Date: Mon Apr 24 07:34:51 2017 New Revision: 247090 URL: https://gcc.gnu.org/viewcvs?rev=247090=gcc=rev Log: 2017-04-24 Richard Biener PR c++/2972 *

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 Bug 2972 depends on bug 19808, which changed state. Bug 19808 Summary: miss a warning about uninitialized member usage in member initializer list in constructor https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19808 What|Removed

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 Bug 2972 depends on bug 19808, which changed state. Bug 19808 Summary: miss a warning about uninitialized member usage in member initializer list in constructor https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19808 What|Removed

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 Richard Biener changed: What|Removed |Added CC||adl at gnu dot org --- Comment #23 from

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 Manuel López-Ibáñez manu at gcc dot gnu.org changed: What|Removed |Added CC||rguenth at

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 --- Comment #20 from Manuel López-Ibáñez manu at gcc dot gnu.org --- (In reply to Jonathan Wakely from comment #14) Created attachment 20817 [details] better -Wmeminit patch This version ignores empty classes and checks for a nontrivial

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 Paolo Carlini paolo.carlini at oracle dot com changed: What|Removed |Added CC|gcc-bugs at gcc dot gnu.org | ---

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 --- Comment #18 from Jonathan Wakely redi at gcc dot gnu.org 2012-08-21 17:26:16 UTC --- No, not at present. I tried using default_init_uninitialized_part but it either missed cases or produce ICEs, and I never solved the problems. I can send you

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 --- Comment #19 from Paolo Carlini paolo.carlini at oracle dot com 2012-08-21 17:54:12 UTC --- Eh, I'm of course not sure that I can help but I quickly went through the exchange on gcc-patches and got the impression that your work was already in

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 --- Comment #16 from Jonathan Wakely redi at gcc dot gnu.org 2011-11-07 21:45:44 UTC --- new patch http://gcc.gnu.org/ml/gcc-patches/2011-11/msg01068.html

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2972 Jonathan Wakely redi at gcc dot gnu.org changed: What|Removed |Added Attachment #20817|0 |1 is

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

--- Comment #10 from manu at gcc dot gnu dot org 2010-06-03 08:47 --- (In reply to comment #9) I've been experimenting with this patch, which warns if there is a missing mem-initializer for a scalar. It gives a false positive for cases were the member is assigned to in the

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

--- Comment #11 from jwakely dot gcc at gmail dot com 2010-06-03 09:18 --- (In reply to comment #10) (In reply to comment #9) I've been experimenting with this patch, which warns if there is a missing mem-initializer for a scalar. It gives a false positive for cases were the

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

--- Comment #12 from jwakely dot gcc at gmail dot com 2010-06-03 09:27 --- Apart from the false positives, another problem is that the check for layout_pod_type_p is not right. An empty class is a POD but doesn't need initialising. --

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

--- Comment #13 from paolo dot carlini at oracle dot com 2010-06-03 10:16 --- About -Weffc++, we also have a PR (16166) about splitting it... Not that I think we should really do that - adding a dozen of -Weffc++-type warnings - but I believe it would be a good idea to finally resolve

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

--- Comment #14 from jwakely dot gcc at gmail dot com 2010-06-03 11:24 --- Created an attachment (id=20817) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20817action=view) better -Wmeminit patch This version ignores empty classes and checks for a nontrivial default ctor instead

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

--- Comment #9 from redi at gcc dot gnu dot org 2010-06-03 01:13 --- I've been experimenting with this patch, which warns if there is a missing mem-initializer for a scalar. It gives a false positive for cases were the member is assigned to in the constructor body, or otherwise

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

--- Comment #8 from manu at gcc dot gnu dot org 2010-02-24 13:05 --- Related to PR 19808. (In reply to comment #6) However -Wunitialized is taken over by the middle-end. This is That doesn't mean that you cannot produce uninitialized warnings in the front-end for clear-cut cases

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

--- Comment #7 from bangerth at dealii dot org 2008-09-10 15:30 --- Still the same with gcc version 4.4.0 20080801 (experimental) [trunk revision 138448] -- bangerth at dealii dot org changed: What|Removed |Added

[Bug c++/2972] -Wuninitialized could warn about uninitialized member variable usage in constructors

--- Comment #6 from gdr at gcc dot gnu dot org 2006-01-22 03:43 --- (In reply to comment #5) Also, it should detect any scalar member variables that are not assigned to in any way in the constructor. Agreed. However -Wunitialized is taken over by the middle-end. This is one more