[XLC++] warning 1540-0183 on explicit instantiation
---------------------------------------------------

                 Key: STDCXX-367
                 URL: https://issues.apache.org/jira/browse/STDCXX-367
             Project: C++ Standard Library
          Issue Type: Bug
          Components: Build
    Affects Versions: 4.1.3
         Environment: IBM XLC++ 7.0
            Reporter: Martin Sebor
            Priority: Minor


Compiling stdcxx 4.1.3 with XLC++ 7.0 on AIX produces many warnings like the 
ones below:

xlCcore -c -I/amd/devco/sebor/stdcxx-4.1.3/include/ansi -D_RWSTDDEBUG    
-D_RWSTD_USE_CONFIG -I/build/sebor/stdcxx-4.1.3-xlc-7.0.0.9-11s/include 
-I/amd/devco/sebor/stdcxx-4.1.3/include  -g  -qtemplateregistry=repository.ti   
 /amd/devco/sebor/stdcxx-4.1.3/src/ti_istream.cpp
"/amd/devco/sebor/stdcxx-4.1.3/include/istream", line 580.23: 1540-0183 (W) The 
explicit instantiation "basic_istream<char,std::char_traits<char> >" should 
either be explictly qualified or be declared in the namespace containing the 
template.
"/amd/devco/sebor/stdcxx-4.1.3/include/istream", line 580.23: 1540-0183 (W) The 
explicit instantiation "basic_istream<char,std::char_traits<char> >" should 
either be explictly qualified or be declared in the namespace containing the 
template.
"/amd/devco/sebor/stdcxx-4.1.3/include/istream", line 153.16: 1540-0700 (I) The 
previous message was produced while processing 
"__rw::__rw_extract<char,std::char_traits<char>,bool>(basic_istream<char,std::char_traits<char>
 > &, bool &)".
"/amd/devco/sebor/stdcxx-4.1.3/include/istream", line 152.20: 1540-0700 (I) The 
previous message was produced while processing 
"std::basic_istream<char,std::char_traits<char> >::operator>>(bool &)".
"/amd/devco/sebor/stdcxx-4.1.3/include/istream", line 82.7: 1540-0700 (I) The 
previous message was produced while processing "class 
std::basic_istream<char,std::char_traits<char> >".
...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to