Programming bug or icc bug?

Sinedie · 06-12-2009, 03:29 AM

Hello,
I have the following code that compiles with g++ (4.3.2) without any warning and runs smoothly with "-ansi -pedantic -Wall". But it does not compile with Intel C++ compiler (icc, v10.1). The following is the code:

Code:

#include <iostream>

using namespace std;

class Add {
        private:
                int dx;

        public: 
                Add() : dx(0) {}

                Add(int _dx) : dx(_dx) {}

                int operator() (int n)
                {
                        return n+dx;
                } 
};

int main()
{
        Add add_0;
        Add add_5(5);

        cout << add_0(100) << endl;
        cout << add_5(100) << endl;

        return 0;
}

The error with icc is:

Code:

/usr/include/c++/4.3.2/bits/char_traits.h(266): error: identifier "__builtin_memchr" is undefined
        { return static_cast<const char_type*>(__builtin_memchr(__s, __a, __n)); }
                                               ^

/usr/include/c++/4.3.2/bits/char_traits.h(270): error: identifier "__builtin_memmove" is undefined
        { return static_cast<char_type*>(__builtin_memmove(__s1, __s2, __n)); }
                                         ^

/usr/include/c++/4.3.2/bits/allocator.h(143): error: identifier "__is_empty" is undefined
    template<typename _Alloc, bool = __is_empty(_Alloc)>
                                     ^

/usr/include/c++/4.3.2/bits/allocator.h(143): error: function call is not allowed in a constant expression
    template<typename _Alloc, bool = __is_empty(_Alloc)>
                                     ^

/usr/include/c++/4.3.2/bits/allocator.h(143): error: type name is not allowed
    template<typename _Alloc, bool = __is_empty(_Alloc)>
                                                ^

/usr/include/c++/4.3.2/bits/allocator.h(160): error: identifier "__is_empty" is undefined
    template<typename _Alloc, bool = __is_empty(_Alloc)>
                                     ^

/usr/include/c++/4.3.2/bits/allocator.h(160): error: function call is not allowed in a constant expression
    template<typename _Alloc, bool = __is_empty(_Alloc)>
                                     ^

/usr/include/c++/4.3.2/bits/allocator.h(160): error: type name is not allowed
    template<typename _Alloc, bool = __is_empty(_Alloc)>
                                                ^

/usr/include/c++/4.3.2/bits/locale_facets.tcc(1284): error: class "std::ctype_byname<char>" is not an entity that can be instantiated
    extern template class ctype_byname<char>;
                    ^

/usr/include/c++/4.3.2/bits/locale_facets.tcc(1319): error: class "std::ctype_byname<wchar_t>" is not an entity that can be instantiated
    extern template class ctype_byname<wchar_t>;
                    ^

compilation aborted for function_objects.cpp (code 2)

Help please!

TIA,
-S

giftlftr_23 · 06-12-2009, 03:41 AM

I never used a icc before but I'm guessing the icc is using the g++ includes not its own includes.

Sinedie · 06-12-2009, 03:47 AM

Yes, I tried reinstalling it. It didn't work. ICC uses its env variables set in iccvars.sh. So that should not be a reason.

giftlftr_23 · 06-12-2009, 03:53 AM

Why not post in icc support?

Sinedie · 06-12-2009, 04:07 AM

Because I was not sure if it was something that conforms to C++ standards (despite -ansi -pedantic -Wall). This was the first time I used something like x(0) which I did not see earlier in the material I read to be a proper way to initialize.

colucix · 06-12-2009, 04:16 AM

It compiles well using icpc on my system (CentOS 5.3), just doing

Code:

icpc code.c

.

giftlftr_23 · 06-12-2009, 04:17 AM

The problem is not something to do with the conformance with standard c++ syntax but about the wrong includes your icc is reading. Post this problem to the icc support so that they can help with your problem.

Sinedie · 06-12-2009, 12:43 PM

I downloaded the latest icc. It works with issues. Will post it in the Intel forum as a bug report.

colucix · 06-12-2009, 01:02 PM

Have you tried with icpc (the intel C++ compiler)? If I try to compile it using icc I get a catastrophic error, whereas using icpc it compiles without a glitch.

Sinedie · 06-13-2009, 01:51 AM

It gave the same error with both with v10.1.008. With the current version (v11) even icc works.