This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
-O3 -> warning: xxx might be used uninitialized (STL)
- To: GNUWin32 <gnu-win32 at cygnus dot com>
- Subject: -O3 -> warning: xxx might be used uninitialized (STL)
- From: Brian Osman <bosman at clariion dot com>
- Date: Fri, 07 Aug 1998 10:20:53 -0500
I couldn't find any mention of this in the mailing list archives, or in
the egcs archives. I'm using B19.1, with egcs 1.0.2. I have a
substantial program I'm working on, which uses STL pretty heavily.
Whenvever I'm doing normal builds (i.e. -g -Wall) everything goes fine,
but as soon as I replace -g with -O3, I get thousands (actually 1028)
of warnings in the stl headers, and some other standard headers about
unitialized variables. Is this normal? Or has it been corrected at some
point? After eliminating all the duplicates, it looks like there's 65
such unique warnings being generated, all in:
fstream.h
std/bastring.h
stl_alloc.h
stl_construct.h
stl_list.h
stl_tree.h
stl_unitialized.h
stl_vector.h
Thanks for any suggestions...
Brian
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".