incompatibility of PGI compiler ?

[Toon Knapen]

Following small test-program (see below) compiles fine with multiple
versionS of gcc, icc, xlC, aCC, pathscale but not with the PGI compiler.
The PGI 6.1 compiler tells me following:

<error>
"test.cpp", line 12: error: more than one operator "<<" matches these
operands:
function "std::operator<<(std::basic_ostream<char,
std::char_traits<char>> &, const
std::complex<double> &)"
function "mine::operator<<(std::ostream &, const
std::complex<double> &)"
operand types are: std::ostream << std::complex<double>
std::cout << d << std::endl ;
^

1 error detected in the compilation of "test.cpp".
</error>

Now I'm wondering if PGI is right or all others are right? Due to Koenig
lookup the compiler logically is going to search in the std namespace
too so the error generated by PGI looks plausible.

Additionally, does anybody know of any unconforming behaviour of the PGI
compiler ?

Thanks,

toon
<test.cpp>
#include <complex>
#include <iostream>

namespace mine {

std::ostream& operator<<(std::ostream& os,std::complex<double> const & v)
{ std::cout << "mine::operator<<" << std::endl ; return os ; }

void foo()
{
std::complex<double> d ;
std::cout << d << std::endl ;
}
}
</test.cpp>

[Bob Hairgrove]

On Fri, 03 Mar 2006 13:25:52 +0100, Toon Knapen
<"reverse[nepank.noot]"@fft.be> wrote:

Following small test-program (see below) compiles fine with multiple
versionS of gcc, icc, xlC, aCC, pathscale but not with the PGI compiler.
What compiler is this?
The PGI 6.1 compiler tells me following:

<error>
"test.cpp", line 12: error: more than one operator "<<" matches these
operands:
function "std::operator<<(std::basic_ostream<char,
std::char_traits<char>> &, const
std::complex<double> &)"
function "mine::operator<<(std::ostream &, const
std::complex<double> &)"
operand types are: std::ostream << std::complex<double>
std::cout << d << std::endl ;
^

1 error detected in the compilation of "test.cpp".
</error>

Now I'm wondering if PGI is right or all others are right? Due to Koenig
lookup the compiler logically is going to search in the std namespace
too so the error generated by PGI looks plausible.

Additionally, does anybody know of any unconforming behaviour of the PGI
compiler ?

Thanks,

toon
<test.cpp>
#include <complex>
#include <iostream>
You should also #include <ostream> here...
namespace mine {

std::ostream& operator<<(std::ostream& os,std::complex<double> const & v)
{ std::cout << "mine::operator<<" << std::endl ; return os ; }

void foo()
{
std::complex<double> d ;
std::cout << d << std::endl ;
}
}
</test.cpp>

Your code compiles and runs fine on MSVC++ ver. 7.1. Looks like a bug
in your compiler to me.

--
Bob Hairgrove
No**********@Home.com

[Toon Knapen]

Bob Hairgrove wrote:

On Fri, 03 Mar 2006 13:25:52 +0100, Toon Knapen
<"reverse[nepank.noot]"@fft.be> wrote:

Following small test-program (see below) compiles fine with multiple
versionS of gcc, icc, xlC, aCC, pathscale but not with the PGI compiler.

What compiler is this?

PGI? See http://www.pgroup.com/
xlC is IBM's compiler on IBM Aix

There are pretty well known for generating efficient code just like the
pathscale compiler.
Your code compiles and runs fine on MSVC++ ver. 7.1. Looks like a bug
in your compiler to me.

Probably but I'm trying to figure out on what grounds (i.e. based on
which paragraph(s) in the standard) ?

toon