uninitialized var in list

Code:

---

#include <list>
#include <string>
using namespace std;
int main ()
{
  list<string> mylist;
  mylist.push_back("test");
}

---

Generates this warning.

Quote:

---

..\include\c++\3.4.5\bits\stl_list.h:435: warning: '__p' might be used uninitialized in this function

---

Now I'm not inclined to surf through cryptic library code, but I'm assuming the most basic use of a list should at least compile warning-free.

What compiler and what version?

gcc 4.2.3 on Linux gives me no warning/error even with "-Wall -pedantic -ansi".

occurs in both MingW 3.4.4 and 3.4.5 with -w and -pedantic -errors
I wonder if this is why I get so many retarded warnings with C++....

Strangely (and yet as expected), I get no warnings when I compile that program with the MinGW port of g++ 3.4.5 on Windows XP SP3.

Hmm yeah, I've just tried invoking mingw32-g++ -w -pedantic directly from the command shell and all seems well....

Well I thought my IDE was purely evil, until I disabled optimizations, and bingo!
So I tried:

Code:

---

mingw32-g++ test.cpp -Wall -s -Os -O3 -fexpensive-optimizations

---

and got it to repro.
Maybe it's common knowledge, but I was under the impression that compiler optimizations should have no affect on compile-time standards compliance.

FWIW: with a few different versions of g++ (4.1, 4.2, and 4.3) under Linux, I get no such warning.

Code:

---

$ cat list.cpp
#include <list>
#include <string>
using namespace std;
int main ()
{
  list<string> mylist;
  mylist.push_back("test");
}
$ g++
g++      g++-4.1  g++-4.2  g++-4.3
$ g++ --version
g++ (Debian 4.3.1-9) 4.3.1
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ g++ -Wall -s -Os -O3 -fexpensive-optimizations list.cpp -o list
$ g++-4.2 -Wall -s -Os -O3 -fexpensive-optimizations list.cpp -o list
$ g++-4.1 -Wall -s -Os -O3 -fexpensive-optimizations list.cpp -o list
$

---

Yeah, GCC only gives such warnings if it computes control and data flow, which it does only when optimizing.

Possibly 3.4.5's standard library has a bug. The problem of the MinGW project is that they're so far behind in the supported compiler version.

I always use this distribution when I'm on Windows

http://nuwen.net/mingw.html

They have gcc 4.2.1 and includes several common libraries (boost, SDL, etc).