search for: fixed_intrin_sse2

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

2014 Jun 28
0
[PATCH 14] preprocessor macros in lpc_intrin_sseN.c
...and DATA_RESULT. This patch changes their names so they become different. Reason: FLAC build systems don't apply specific options (such as -msse4.1) to specific files. So it makes little sense to have separate *_intrin_sseA.c and *_intrin_sseB.c files. IMHO it's not unreasonable to merge fixed_intrin_sse2.c and fixed_intrin_sse2.c into fixed_intrin.c, etc. This patch makes it possible for lpc_intrin_sse2.c and lpc_intrin_sse41.c. -------------- next part -------------- A non-text attachment was scrubbed... Name: 14_sse_define.patch Type: application/octet-stream Size: 17501 bytes Desc: not available...
2014 Aug 13
1
[PATCH] simpler xmm -> int64 code
This patch simplifies XMM -> int64 conversion in fixed_intrin_sse2.c and fixed_intrin_ssse3.c -------------- next part -------------- A non-text attachment was scrubbed... Name: fixed_sse.zip Type: application/zip Size: 778 bytes Desc: not available Url : http://lists.xiph.org/pipermail/flac-dev/attachments/20140813/49f18196/attachment.zip
2014 Apr 09
2
Patch to fix compiler warnings and error status collisions
Erik de Castro Lopo wrote: > This could also be fixed by adding a: > > decoder->protected_->initstate > > and using that correctly. Right? > > I'm going to play with this idea. That fixed it. Commit is here: https://git.xiph.org/?p=flac.git;a=commit;h=3f5208c30022b7cbd0b9095ad3550c4f6cb348c9 What didn't get added was this: diff --git
2014 Apr 11
0
Patch to fix compiler warnings and error status collisions
...ANDROID__'. Note, this compiler warning was generated when compiling on Mac OSX 10.9 with clang: utils.c:189:6: warning: implicit declaration of function 'ioctl' is invalid in C99 [-Wimplicit-function-declaration] Also, at the moment, TOT does not compile. It is missing the file fixed_intrin_sse2.c -Lenny On Wed, Apr 9, 2014 at 2:12 AM, Erik de Castro Lopo <mle+la at mega-nerd.com>wrote: > Erik de Castro Lopo wrote: > > > This could also be fixed by adding a: > > > > decoder->protected_->initstate > > > > and using that correctly. Righ...