[Bug c++/52167] self-assignment should at least produce use-of-uninitialized warning

2017-11-08 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52167

Martin Sebor  changed:

   What|Removed |Added

 CC||antoshkka at gmail dot com

--- Comment #6 from Martin Sebor  ---
*** Bug 82900 has been marked as a duplicate of this bug. ***

[Bug c++/52167] self-assignment should at least produce use-of-uninitialized warning

2017-03-03 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52167

Manuel López-Ibáñez  changed:

   What|Removed |Added

 CC||appfault at hotmail dot com

--- Comment #5 from Manuel López-Ibáñez  ---
*** Bug 70991 has been marked as a duplicate of this bug. ***

[Bug c++/52167] self-assignment should at least produce use-of-uninitialized warning

2012-10-25 Thread manu at gcc dot gnu.org

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52167

Manuel López-Ibáñez manu at gcc dot gnu.org changed:

   What|Removed |Added

 CC||miles at gnu dot org

--- Comment #4 from Manuel López-Ibáñez manu at gcc dot gnu.org 2012-10-25 
09:15:35 UTC ---
*** Bug 53287 has been marked as a duplicate of this bug. ***


[Bug c++/52167] self-assignment should at least produce use-of-uninitialized warning

2012-02-08 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52167

Jonathan Wakely redi at gcc dot gnu.org changed:

   What|Removed |Added

   Keywords||diagnostic
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2012-02-08
 Ever Confirmed|0   |1

--- Comment #1 from Jonathan Wakely redi at gcc dot gnu.org 2012-02-08 
09:03:41 UTC ---
You need -Winit-self, but it doesn't work for class types.


[Bug c++/52167] self-assignment should at least produce use-of-uninitialized warning

2012-02-08 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52167

Richard Guenther rguenth at gcc dot gnu.org changed:

   What|Removed |Added

   Severity|normal  |enhancement


[Bug c++/52167] self-assignment should at least produce use-of-uninitialized warning

2012-02-08 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52167

Manuel López-Ibáñez manu at gcc dot gnu.org changed:

   What|Removed |Added

 CC||manu at gcc dot gnu.org

--- Comment #2 from Manuel López-Ibáñez manu at gcc dot gnu.org 2012-02-08 
14:01:05 UTC ---
Clang++ 3.0 warns:

/tmp/webcompile/_14716_2.cc:8:20: warning: variable 'foo' is uninitialized when
used within its own initialization [-Wuninitialized]
  const string foo(foo);
   ~~~ ^~~
1 warning generated.

Clang improves a lot every 6 months, you should always check the latest version
(or SVN if possible).


[Bug c++/52167] self-assignment should at least produce use-of-uninitialized warning

2012-02-08 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52167

Andrew Pinski pinskia at gcc dot gnu.org changed:

   What|Removed |Added

 Depends on||48829, 48483

--- Comment #3 from Andrew Pinski pinskia at gcc dot gnu.org 2012-02-09 
07:42:33 UTC ---
Related to PR 48829 and PR 48483.