search for: _flac__cpu_info_x86

Displaying 4 results from an estimated 4 matches for "_flac__cpu_info_x86".

Did you mean: flac__cpu_info_x86
2016 Jun 26
4
FLAC__SSE_OS change
...s. > It can be fixed by adding "#include share/compat.h" to cpu.c (or by using > FLAC__uint32 from FLAC/ordinals.h). Ok, added share/compat.h. > When I fix this, the following problem occurs: > > error LNK2019: unresolved external symbol ___cpuidex referenced in function _FLAC__cpu_info_x86 libflac_static.lib > fatal error LNK1120: 1 unresolved externals flac.exe > > The code > > if (FLAC__AVX_SUPPORTED) > __cpuidex(cpuinfo, level, 0); /* for AVX2 detection */ > else > __cpuid(cpuinfo, level); /* some old compilers don't suppor...
2016 Jun 26
5
FLAC__SSE_OS change
First off, this code is horrible to read and work on. The recent commits are the first of what I hope is a massive clean up of this code. lvqcl wrote: > So if I understand things correctly, the current meaning of --(en|dis)able-sse is: > > on Linux: > --enable-sse: > add -msse2 to the compiler switches > do not test SSE OS support (assume that SSE is
2016 Jun 26
2
FLAC__SSE_OS change
lvqcl wrote: > Sure. > > The question is, what to do with the debug configuration. <sigh/> Is this only a problem with MSVS2005? If so, I'd be inclined to jsut drop support for it. Its over 10 years old and aren't there free versions of more recent MSVCs available? Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo
2016 Jun 26
0
FLAC__SSE_OS change
...>> The question is, what to do with the debug configuration. > > <sigh/> > > Is this only a problem with MSVS2005? No, MSVC 2015 is also affected. I renamed __cpuid() to __cpuid22(), and it wrote: error LNK2019: unresolved external symbol ___cpuid22 referenced in function _FLAC__cpu_info_x86 fatal error LNK1120: 1 unresolved externals So, all currently available MSVC compilers cannot create debug builds for such code. But I have no idea are they really necessary or not. > If so, I'd be inclined to jsut > drop support for it. Its over 10 years old and aren't there fre...