search for: vs2010

When using MS VS2010 there is an issue with std: `SuccIterator` implements a partial assignment operator: inline const _Self &operator=(const _Self &I) { assert(Term == I.Term &&"Cannot assign iterators to two different blocks!"); idx = I.idx; return *this; } Fo...

...5 +- configure.ac | 320 ++++++++++++++++++----------- m4/opus-intrinsics.m4 | 29 +++ silk/x86/SigProc_FIX_sse.h | 17 ++ silk/x86/main_sse.h | 48 +++++ silk/x86/x86_silk_map.c | 25 ++- win32/VS2010/celt.vcxproj | 17 +- win32/VS2010/celt.vcxproj.filters | 27 +++ win32/VS2010/opus_demo.vcxproj | 29 ++- win32/VS2010/opus_demo.vcxproj.filters | 5 + win32/VS2010/silk_common.vcxproj | 15 +- win32/VS2010/silk_common.vcxproj.filters | 21 ++ win32...

Hi Bob, was this issue resolved? Ciao, Duncan. > When using MS VS2010 there is an issue with std: > > `SuccIterator` implements a partial assignment operator: > > inline const _Self &operator=(const _Self &I) { > > assert(Term == I.Term &&"Cannot assign iterators to two different blocks!"); > > idx = I.idx; > >...

here are a couple of patches to address some warnings in Microsoft compilers, and a build error in vs2010 in particular vs2010-errors.patch: In SelectionDAGISel, std::pairs or pointers are being constructed using a 0 as an initializer causes an error inside the std::pair constructor. I think changes to language in support of the nullptr keyword caused this break. vs2010-warnings.patch: This patch fi...

...;> Wow, requiring GCC 4.7 would be really aggressive, it was just >> released in March 2012. Call me conservative, but I was thinking that >> a reasonable GCC baseline would be GCC 4.4 or something (which is ~3.5 >> years old). > > The feature intersection of GCC 4.4 and VS2010 leaves us with auto and > static_assert. Ok, that's too minor to be worth the trouble. Would the intersection of GCC 4.5 VS2010 be practical? -Chris

Orestes Zoupanos wrote: > VS2015, considering it's quite recent and the Community Edition has a > free-to-use-for-open-source license going on. > >>> Yup, into win32\VS2010 and VS2015. >> >> VS2015 or VS2005? Currently FLAC has 2 Visual Studio solutions: one >> for VS2005 >> (and 2008) and another for VS2010 and all newer (2012, 2013, 2015...) Then I don't quite understand. Do you plan to drop support for VS2005/2008? Besides, VS2015 and...

On Mon, Oct 4, 2010 at 9:52 PM, Bob Floyd <bobfloyd at comcast.net> wrote: > When using MS VS2010 there is an issue with std: > > > > `SuccIterator` implements a partial assignment operator: > > > > inline const _Self &operator=(const _Self &I) { > >     assert(Term == I.Term &&"Cannot assign iterators to two different > blocks!"); >...

Michael, Yes, while stepping through this VS2010 `std::swap` code, `_Move` did nothing, e.g. //////////////////////////////////////////////////// void swap(_Ty& _Left, _Ty& _Right) { // exchange values stored at _Left and _Right _Ty _Tmp = _Move(_Left); _Left = _Move(_Right); _Right = _Move(_Tmp); } ///////////////////////////////...

...ep 23, 2010 at 4:04 AM, Michael Spencer <bigcheesegs at gmail.com>wrote: > On Thu, Sep 23, 2010 at 2:40 AM, Nathan Jeffords > <blunted2night at gmail.com> wrote: > > here are a couple of patches to address some warnings > > in Microsoft compilers, and a build error in vs2010 in particular > > vs2010-errors.patch: > > In SelectionDAGISel, std::pairs or pointers are being constructed using > a 0 > > as an initializer causes an error inside the std::pair constructor. I > think > > changes to language in support of the nullptr keyword caused...

On Thu, Sep 23, 2010 at 2:40 AM, Nathan Jeffords <blunted2night at gmail.com> wrote: > here are a couple of patches to address some warnings > in Microsoft compilers, and a build error in vs2010 in particular > vs2010-errors.patch: > In SelectionDAGISel,  std::pairs or pointers are being constructed using a 0 > as an initializer causes an error inside the std::pair constructor. I think > changes to language in support of the nullptr keyword caused this break. Yep, people keep...

...itory: 'C:\My Documents\Opus\win32\..\.git' 1> The syntax of the command is incorrect. 1> The system cannot find the path specified. 1>C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(103,5): error MSB3073: The command ""C:\My Documents\Opus\win32\VS2010\..\..\win32\genversion.bat" "C:\My Documents\Opus\win32\VS2010\..\..\win32\version.h" PACKAGE_VERSION 1>C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(103,5): error MSB3073: :VCEnd" exited with code 1. ========== Build: 0 succeeded, 1 failed, 0 up-to-...

Hi! VS2010 now includes a stdint.h header. LLVM assumes that there is no stdint.h header and creates own types and macros. Because the macros in the stdint.h header are not protected, you get warnings at compile time if you first include llvm/Support/Datatypes.h and then stdint.h. The attached patch inclu...

The attached patch cleans up Opus's x86 intrinsics configury. It: * Makes ?enable-intrinsics work with clang and other non-GCC compilers * Enables RTCD for the floating-point-mode SSE code in Celt. * Disables use of RTCD in cases where the compiler targets an instruction set by default. * Enables the SSE4.1 Silk optimizations that apply to the common parts of Silk when Opus is built in

...AM, Michael Spencer <bigcheesegs at gmail.com>wrote: > >> On Thu, Sep 23, 2010 at 2:40 AM, Nathan Jeffords >> <blunted2night at gmail.com> wrote: >> > here are a couple of patches to address some warnings >> > in Microsoft compilers, and a build error in vs2010 in particular >> > vs2010-errors.patch: >> > In SelectionDAGISel, std::pairs or pointers are being constructed using >> a 0 >> > as an initializer causes an error inside the std::pair constructor. I >> think >> > changes to language in support of the...

I'm getting errors like so on initial build of libtheora - 1>c1 : fatal error C1083: Cannot open source file: '..\lib\dec\x86_vc\x86stat.c': No such file or directory 1> mmxstate.c (TaskId:16) 1>c1 : fatal error C1083: Cannot open source file: '..\lib\dec\x86_vc\mmxstate.c': No such file or directory 1> mmxloopfilter.c (TaskId:16) 1>c1 : fatal error C1083:

"Bill O'Hara" <billtohara at gmail.com> writes: > 1>LLVMX86CodeGen.lib(X86JITInfo.obj) : error LNK2019: unresolved > external symbol X86CompilationCallback referenced in function "public: > virtual void (__cdecl*__cdecl > llvm::X86JITInfo::getLazyResolverFunction(void * (__cdecl*)(void > *)))(void)" (?getLazyResolverFunction at

Constructing LLVMBuild project information CMake Error at CMakeLists.txt:299 (message): Unexpected failure executing llvm-build: Traceback (most recent call last): File "C:/OpenSource/llvm/utils/llvm-build/llvm-build", line 3, in <module> import llvmbuild File "C:\OpenSource\llvm\utils\llvm-build\llvmbuild\__init__.py", line 1, in <module> from main import

...the windows build automatically do the sanest possible thing, > preferably with anyone having to copy files. The way we've been doing the Opus stuff is to have the project files expect a build in a parallel checkout. so: c:\dev\flac\FLAC.sln expects to find an ogg build in c:\dev\ogg\win32\VS2010\ Not as obvious as having a monolithic build, but it seems to work once you've figured it out. And each arch and target can reference the corresponding target in the dependency. -r

...jections/tips or reasons to leave them as is? > > Lvqcl and other Windows devs? > > I'm ok with this if you are. I don't care much actually... THough I'd like to know exactly what files will be moved and where. Into 2 new directories "win32\VS2005" and "win32\VS2010", or somewhere else? Maybe it's better to ask those who use libFLAC in their Windows programs. Audacity devs? Winamp devs? Somebody else?

Hello, Following some recent messages about building with Visual Studio 2010, I have gotten most things to compile in release mode on 64b windows 7. (Mainly the few errors with 0 -> nullptr in the second argument of the pair constructor, and making an ECValue constructor public). I'm falling at the last hurdle though when it comes to the final link: 1>------ Build started: Project: