[Bug libstdc++/19343] [4.0 Regression] New warnings in libstdc++-v3 since 2004-01-05

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2005-01-14 14:45 -------
Actually this is not a middle-end after all.
The problem is that __throw_bad_alloc is not marked as noreturn as it should be.

"In the if-part, the function either (a) returns, from the while-loop; 
or (b) throws.  In the else-part, it does return. "

Yes it throws but since libstdc++ use a function call to throw, well GCC does not know that function 
can return since it is not marked as noreturn.

The patch which caused this warning:
2005-01-05  Benjamin Kosnik  <bkoz@redhat.com>
        * src/bitmap_allocator.cc: Use __throw_bad_alloc. 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bkoz at gcc dot gnu dot org,
                   |                            |gdr at gcc dot gnu dot org
          Component|middle-end                  |libstdc++


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