[gecode-users] EXTERNAL: RE: Compilation trouble in 64 bit environment?

[Maity, Ashis K]

Christian, 

It is MSVC 2008 (Microsoft Visual Studio 9.0). Our IT installed that in my computer and it had several issues. I had to reinstall Windows SDK and a few other things. Now I can at least compile and run. But it appears something is not right as some memory spikes are really scary. Most importantly the memory spike does not occur in the old executable (that I had saved) when I run the same problem. Would reinstalling Visual Studio help? Is it common to have some visual studio files in "C:\Program Files (x86)\" directory and some in "C:\Program Files". Also I have two Windows SDKs (one C:\Program Files (x86) and one in C:\Program Files) -- is that okay? Would you point me to any documentation that have instructions for Gecode and Visual Studio configurations?

Thanks,

Ashis

-----Original Message-----
From: Christian Schulte [mailto:cschulte at kth.se] 
Sent: Friday, July 22, 2011 11:36 AM
To: Maity, Ashis K; users at gecode.org
Subject: EXTERNAL: RE: [gecode-users] Compilation trouble in 64 bit environment?

Well, as you do not tell which version of Visual Studio you use...

 But there are no issues: Gecode compiles and runs just fine with MSVC 2008
and 2010 both for x86 (32 bit) and x64 (64 bit). The MSVC 2010 compilers
seem to use more memory and seem to take more time, but that's fine. The
warnings you get can be safely ignored (we also test for warnings), somehow
you switched on the highest warning level where everything gets you a
warning (try the standard C++ header files to see what I mean).

I myself use Windows 7 and all the different versions of MSVC mentioned
above, so I can't real see any issues.

Best
Christian

--
Christian Schulte, KTH, web.it.kth.se/~cschulte/

-----Original Message-----
From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of Maity, Ashis K
Sent: Friday, July 22, 2011 5:11 PM
To: cschulte at kth.se; users at gecode.org
Subject: [gecode-users] Compilation trouble in 64 bit environment?

Hi All,

I have recently upgraded my computer to 64 bit Windows 7 and new visual
Studio installation. After this I get a bunch of warnings like the following
and the compilation takes a long time. Worse, while running the same
problem, the new environment consumes a ton of memory. Did anybody
experience similar issues? Any feedback is appreciated.

Thanks,

Ashis

C:\data\amaity\Gecode36\include\gecode/support/exception.hpp(46) : warning
C4275: non dll-interface class 'std::exception' used as base for
dll-interface class 'Gecode::Exception'
1>        C:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\include\exception(95) : see declaration of 'std::exception'
1>        C:\data\amaity\Gecode36\include\gecode/support/exception.hpp(46) :
see declaration of 'Gecode::Exception'
1>C:\data\amaity\Gecode36\include\gecode/kernel/archive.hpp(246) : warning
C4800: 'unsigned int' : forcing value to bool 'true' or 'false' (performance
warning)
1>C:\data\amaity\Gecode36\include\gecode/kernel/region.hpp(75) : warning
C4200: nonstandard extension used : zero-sized array in struct/union
1>        Cannot generate copy-ctor or copy-assignment operator when UDT
contains a zero-sized array
1>C:\data\amaity\Gecode36\include\gecode/gist.hh(162) : warning C4251:
'Gecode::Gist::TextOutput::n' : class 'std::basic_string<_Elem,_Traits,_Ax>'
needs to have dll-interface to be used by clients of class
'Gecode::Gist::TextOutput'
1>        with
1>        [
1>            _Elem=char,
1>            _Traits=std::char_traits<char>,
1>            _Ax=std::allocator<char>
1>        ]
1>C:\data\amaity\Gecode36\include\gecode/driver.hh(485) : warning C4251:
'Gecode::Options::inspect' : class 'Gecode::Options::_I' needs to have
dll-interface to be used by clients of class 'Gecode::Options'
1>        C:\data\amaity\Gecode36\include\gecode/driver.hh(447) : see
declaration of 'Gecode::Options::_I'
1>C:\data\amaity\Gecode36\include\gecode/driver/options.hpp(319) : warning
C4800: 'int' : forcing value to bool 'true' or 'false' (performance warning)
1>.\Scheduler.cpp(178) : warning C4267: 'initializing' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(220) : warning C4267: 'initializing' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(245) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(366) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(465) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(466) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(472) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(473) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(486) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(486) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(489) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(506) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(551) : warning C4267: 'initializing' : conversion from
'size_t' to 'unsigned int', possible loss of data
1>.\Scheduler.cpp(609) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(609) : warning C4267: 'argument' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(655) : warning C4267: 'initializing' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(666) : warning C4267: 'initializing' : conversion from
'size_t' to 'int', possible loss of data
1>.\Scheduler.cpp(679) : warning C4267: 'initializing' : conversion from
'size_t' to 'int', possible loss of data
1>C:\data\amaity\Gecode36\include\gecode/support/heap.hpp(358) : warning
C4345: behavior change: an object of POD type constructed with an
initializer of the form () will be default-initialized
1>        C:\data\amaity\Gecode36\include\gecode/support/heap.hpp(376) : see
reference to function template instantiation 'T
*Gecode::Heap::alloc<Gecode::DFA::Transition>(unsigned long)' being compiled
1>        with
1>        [
1>            T=Gecode::DFA::Transition
1>        ]
1>        C:\data\amaity\Gecode36\include\gecode/int/extensional/dfa.hpp(87)
: see reference to function template instantiation 'T
*Gecode::Heap::alloc<Gecode::DFA::Transition>(int)' being compiled
1>        with
1>        [
1>            T=Gecode::DFA::Transition
1>        ]

_______________________________________________
Gecode users mailing list
users at gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users