Hi,<br><br>I had to add an include statement for the math header to LiveIntervalAnalysis.h to get it to compile today e.g<br><br>#ifndef LLVM_CODEGEN_LIVEINTERVAL_ANALYSIS_H<br>#define LLVM_CODEGEN_LIVEINTERVAL_ANALYSIS_H<br>
#include <math.h><br><br>It seems then to work without failures; odd.<br><br>However, the deprecation warnings are not suppressed for std::_Uninit_Copy and std::_Copy_Opt (warning 4996) in xutility and memory headers respectively
e.g.<br><br>>C:\Program Files\Microsoft Visual Studio 8\VC\include\memory(93) : warning C4996: 'std::_Uninit_copy' was declared deprecated<br>5> C:\Program Files\Microsoft Visual Studio 8\VC\include\memory(82) : see declaration of 'std::_Uninit_copy'
<br>5> Message: 'You have used a std:: construct that is not safe. See documentation on how to use the Safe Standard C++ Library'<br>5> c:\llvm\include\llvm/ADT/SmallVector.h(427) : see reference to function template instantiation '_FwdIt std::uninitialized_copy<T*,T*>(_InIt,_InIt,_FwdIt)' being compiled
<br>5> with<br>5> [<br>5> _FwdIt=llvm::TargetAlignElem *,<br>5> T=llvm::TargetAlignElem,<br>5> _InIt=llvm::TargetAlignElem *<br>5> ]<br><br>The project would appear to have the right pre-processor definitions to suppress such warnings, but they still occur.
<br><br>The compiler issues _many_ warnings about conversions between uint64_t and uint, which seems to be a very common occurance. Is there any point in LLVM to having such conversions present implicitly vs explicitly (suppressing the warnings?) other than syntactic clarity?