------- Comment #11 from pinskia at gcc dot gnu dot org 2006-01-24 18:19 ------- (In reply to comment #10) > I suppose changing the component to libstc++ was a mistake... Irrespective of > whether the compiler want or not to suppress this warning (in my opinion, it > should not) the logic in the library cannot change.
Actually I moved it on pupose as my testcase shows that this warning is bogus and it is actually a bug in the libstdc++ and not really in the middle-end or the front-end. How would the middle-end know that the assignment is not done even though you are checking if there is error? It cannot know, this again is a libstdc++ bug. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c++ |libstdc++ http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25649