search for: ssex

I have data in a format like this: name ssex sex view num rating rt ahl4 f m f 56 -108 2246 ahl4 f m f 74 85 1444 ahl4 f m f 52 151 1595 ahl4 f m f 85 1 1447 ahl4 f m f 53 46 1716 ahl4 f m f 37 145 1276 ahl4 f m f 50 98 1465 ahl4 f m f 51 -26 1322 ahl4 f m f 38 -97 1790 ahl4 f m f 14 -158 865 ... ahl4 f m p 43 -136 1669 ahl4 f m p 10 -59 808...

...int to test OS SSE support if a compiler already inserted SSE/SSE2 instructions everywhere (because of -msse2 switch). > The problem is that the OS has > to preserve the XMMS registers when doing a context switch. Once the > kernel is preserving the XMMS registers, I'd assume that all SSEx > instructions should work. If the OS doesn't support SSE instructions but -msse2 option was used then libFLAC will crash: it cannot disable the use of SSE/SSE2 instructions that were generated by the compiler.

...us, Thanks for the report. As far as I can tell, what's happening is that when intrinsics are enabled, we compile all tests with -msse4.1, even when it's only run-time detected. In most cases, that doesn't cause any issue, but sometimes the compiler will take the C code and generate an SSEx instruction on its own. I think this is what's happening for you. The actual encoder and decoder should work fine since they are compiled without -msse except for the files that are behind auto-detect. Jean-Marc On 11/26/2015 01:33 PM, Jesus Cea wrote: > On 26/11/15 16:40, Jean-Marc Valin...

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

...t needs to be fixed. I think the way it works on Linux makes > the most sense. > Doesn't SSE support imply SSE2+ support? The problem is that the OS has to preserve the XMMS registers when doing a context switch. Once the kernel is preserving the XMMS registers, I'd assume that all SSEx instructions should work. I have a '96 install of an OS, it has been upgraded until end of life, and it handles SSE4+ instructions fine even though the instruction set was released more recently then the last kernel. Dave

...report. As far as I can tell, what's happening is that > when intrinsics are enabled, we compile all tests with -msse4.1, even > when it's only run-time detected. In most cases, that doesn't cause > any issue, but sometimes the compiler will take the C code and > generate an SSEx instruction on its own. I think this is what's > happening for you. The actual encoder and decoder should work fine > since they are compiled without -msse except for the files that are > behind auto-detect. Good guess. I have tried this: 1. Compile everything as is. 2. "make ch...

...s I can tell, what's happening is >> that when intrinsics are enabled, we compile all tests with >> -msse4.1, even when it's only run-time detected. In most cases, >> that doesn't cause any issue, but sometimes the compiler will >> take the C code and generate an SSEx instruction on its own. I >> think this is what's happening for you. The actual encoder and >> decoder should work fine since they are compiled without -msse >> except for the files that are behind auto-detect. > > Good guess. I have tried this: > > 1. Compile ev...

Hi everyone, After much waiting, Opus 1.1.1 is finally here. The main changes are: - x86 SSE, SSE2 and SSE4.1 optimizations contributed by Cisco, - MIPS optimizations contributed by Imagination Technologies, - ARM Neon optimizations contributed by Linaro and ARM, - many architecture-independent optimizations, - memory footprint reductions, and - several minor bug fixes. The quality of the