search for: intrinics

Hi, Here are 3 suggested patches. 1. Build test for cmake and run the test in gitlab-ci. 2. Disable the message box on Windows on abort that cause test hangs in CI. 3. Build time improvement by removing unnecessary includes of stdio.h in production code and change to a lighter header intrin.h -> intrin0.h (windows only). Attached screenshot of measurement but it resulted in 14%

...r placed in a header. I'll fix that. > 3. denoise.c doesn't seem to be in tar.gz, it is in the visual studio > project file though. The project file isn't up-to-date (I've never even compiled Speex in Win32). The file's been renamed to preprocess.h > We ran the SSE intrinics code through some test on windows over here and > all I can say is - it sucks. A room filled with Monkeys could generate > better SSE code. Having stated that let me describe why. You mean a room filled with monkeys could generate a better compiler? :) > We use Visual Studio 6, SP5 wit...

...earch_sse.h line 34. 2. Compile Error with quant_lsp.c line 55. M_PI is undefined. Either it needs to be included in that file or placed in a header. 3. denoise.c doesn't seem to be in tar.gz, it is in the visual studio project file though. Now onto the actual SSE tests. We ran the SSE intrinics code through some test on windows over here and all I can say is - it sucks. A room filled with Monkeys could generate better SSE code. Having stated that let me describe why. We use Visual Studio 6, SP5 with the processor pack as the main development platform. For some unknown reason, it decid...

> Good catch on the debug mode. After compiling the same code in > release mode it does appear to be using all the registers correctly. Give > us a few days to integrate our run-time flags into 1.1.4 and I will let you > know how are testing turns out. Just a note. With the last optimization I did in cb_search.c, it's no longer easy to have a run-time SSE flag. The

...x that. > > > 3. denoise.c doesn't seem to be in tar.gz, it is in the visual studio > > project file though. > >The project file isn't up-to-date (I've never even compiled Speex in >Win32). The file's been renamed to preprocess.h > > > We ran the SSE intrinics code through some test on windows over here and > > all I can say is - it sucks. A room filled with Monkeys could generate > > better SSE code. Having stated that let me describe why. > >You mean a room filled with monkeys could generate a better compiler? :) > > > We use...

Makes sense, yeah, trying something in a different environment is usually a good way to find problems. I had indeed moved the renamed clang-cl.exe to a different directory, but when I move it back into its home directory and retry the build, I get the same errors. On Thu, Jun 11, 2015 at 11:16 PM, Reid Kleckner <rnk at google.com> wrote: > Thanks for trying the self-host, it's

Jean-Marc, Are you sure that you don't need to add just -msse to enable the intrinsics rather than a full fledged -march=pentium3? I did some playing around and I can get intrinsics code to compile with -march=i686 -msse on linux with that. Check out:

Sorry about that, let me check the correct version for the intrin0.h include guard. //Marcus ________________________________ From: Ralph Giles <giles at thaumas.net> Sent: Thursday, June 11, 2020 19:31 To: Marcus Asteborg <xnorpx at outlook.com>; opus at xiph.org <opus at xiph.org> Subject: Re: [opus] Misc patches Speaking of needing more complete ci feedback, the intrin0.h

On Sat, Dec 02, 2023 at 10:24:57PM +0300, Vitaly Chikunov wrote: > JFYI. I am not sure it's worth reporting but, when building 2.5.5 for ALT Talking of small inconsistencies, 2.5.5 isn't a Xapian version... > I noticed small inconsistencies in configure output. > > 1. xapian-binding: > > checking for /usr/bin/rdoc... no > checking for rdoc... /usr/bin/rdoc >

OK, fixed the problem with the intrin.h header that doesn't exist in previous versions of VS... -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: JIT.patch URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060126/7e55b0d0/attachment.ksh>

3, no good catch attached is an updated patch //Marcus ________________________________ From: Jean-Marc Valin <jmvalin at jmvalin.ca> Sent: Thursday, June 11, 2020 10:49 To: Marcus Asteborg <xnorpx at outlook.com>; opus at xiph.org <opus at xiph.org> Subject: Re: [opus] Misc patches On 2020-06-08 01:39, Marcus Asteborg wrote: > 1. Build test for cmake and run the test in

I'm getting compile errors because size_t is getting redefined. My "forced include file" starts with: #if BUILDING_FOR_WINDOWS #define NOMINMAX /* deal with the fact that windef.h also defines BOOL */ #define BOOL WINBOOL #include <windows.h> #include <intrin.h> #undef BOOL #endif Looking at the preprocessor expansion of a typical .cpp file, I see that crtdefs.h

Hello Erik, Thank you to work. I have not checked to build them, though, I can tell you some comments, excuse me. * General - Please post patches to cfe-commits and to llvm-commits, too. (IMHO it would not be needed to split articles apart each lists as long as each would be related.) - If you can, please attach files w/o CRLF(dos encodings), or with attached text/plain. - You may

Hi, JFYI. I am not sure it's worth reporting but, when building 2.5.5 for ALT I noticed small inconsistencies in configure output. 1. xapian-binding: checking for /usr/bin/rdoc... no checking for rdoc... /usr/bin/rdoc Looks curious but no problem since it's found anyway. 2. xapian-core when built with GCC: checking whether __builtin_add_overflow is declared... yes ...

Hi Reid, I copied the x64 toolsets by hand; they got installed to C:\Program Files (x86)\LLVM\tools\msbuild\x64; they just didn't get moved correctly by install.bat. I just verified that the LLVM-vs2013 toolset.props is correct. If it is a bitness problem, perhaps I'm failing to define something correctly? Regards, Eric On 9/30/14, 11:29 AM, Reid Kleckner wrote: > This looks

I tried checking out the latest llvm/clang from SVN (as of a few hours ago) and compiling it (clang 3.6.1 doesn't compile 3.7 because it fails a version check, so I repeated the technique of compiling with Microsoft C++ first, then using the resulting clang-cl.exe). It fails with a bunch of error messages along the lines of: LLVMSupport.lib(Atomic.obj) : error LNK2019: unresolved external

On Fri, Sep 16, 2016 at 10:54 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > Can you look for the specific errors in the CMake log and error files? > > CMake is very good at not presenting the real issue… > Here it is trying to build very simple programs to check features > availability. Like: > > #include <strings.h> > int main() { ffs(0); return 0;

I believe that we provide a definition of size_t inside the compiler itself when clang is in MSVC compatibility mode. On Tue, Sep 30, 2014 at 5:51 PM, Eric Mader <emader at gmx.us> wrote: > I did some more investigation of the size_t size error. I misunderstood > what was happening. It turns out that size_t is already defined before my > prefix header is included. I added the

Hi Marcus, On 2020-06-08 01:39, Marcus Asteborg wrote: > 1. Build test for cmake and run the test in gitlab-ci. > 2. Disable the message box on Windows on abort that cause test hangs in CI. > 3. Build time improvement by removing unnecessary includes of stdio.h > in production code and change to a lighter header intrin.h -> > intrin0.h (windows only). Attached

On 2020-06-08 01:39, Marcus Asteborg wrote: > 1. Build test for cmake and run the test in gitlab-ci. OK, merged. > 2. Disable the message box on Windows on abort that cause test hangs in CI. Merged too. > 3. Build time improvement by removing unnecessary includes of stdio.h > in production code and change to a lighter header intrin.h -> > intrin0.h (windows only).