[4.0.x] may reach end warning in system headers

Geoff Keating geoffk@apple.com
Fri Jul 1 19:08:00 GMT 2005


On 01/07/2005, at 11:32 AM, Andrew Pinski wrote:

>
> On Jul 1, 2005, at 2:30 PM, Geoffrey Keating wrote:
>
>
>>
>> One of our users was getting
>>
>> /usr/include/gcc/darwin/4.0/c++/bits/stl_uninitialized.h:113:  
>> warning:
>> control may reach end of non-void function '_ForwardIterator
>> std::__uninitialized_copy_aux(_InputIterator, _InputIterator,
>> _ForwardIterator, __false_type) [with _InputIterator =
>> __gnu_cxx::__normal_iterator<TPoolAllocator::tAllocState*,
>> std::vector<TPoolAllocator::tAllocState,
>> std::allocator<TPoolAllocator::tAllocState> > >, _ForwardIterator =
>> __gnu_cxx::__normal_iterator<TPoolAllocator::tAllocState*,
>> std::vector<TPoolAllocator::tAllocState,
>> std::allocator<TPoolAllocator::tAllocState> > >]' being inlined
>>
>
> This is PR 21951 which should be worked around in libstdc++ instead
> of in GCC or at that least that is what was decided.

It's wrong that the compiler is warning about a system header, even  
if libstdc++ should be changed to fix this one instance.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2408 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20050701/17e087c8/attachment.p7s>


More information about the Gcc-patches mailing list