search for: codifications

Hi all, I'm trying to use libspeex 1.1.10 on an ARM926EJ-Sid(wb) rev 3 (v5l). I executed the speexenc and speexdec test files and they can encode and decode. But I'm getting 95% of cpu utilization on the codification and 44% on the decodification. I saw in the post: http://lists.xiph.org/pipermail/speex-dev/2005-June/003485.html that this version of speex works fine on ARM

Hi, I tried the same options suggested in your post and the problem continues. What do you suggest? 2005/9/15, Jean-Marc Valin <Jean-Marc.Valin@usherbrooke.ca>: > Hi Eduardo, > > All I can say is that the timings you have are a bit odd. What > optimizations options are you using (I suggest -O3)? Also, perhaps you > can try --enable-arm4-asm just in case. I've had the

COM is not a language extension. It is a codification of a fairly obvious but not guaranteed C++ ABI/objectmodel decision. Specifically given C++: class Foo { public: virtual void Abc() = 0; virtual void Def() = 0; }; Foo* foo; foo->Abc(); what is the ABI in terms of C? Note well the "virtual" and "=0". They are important. COM declares

Hi Eduardo, All I can say is that the timings you have are a bit odd. What optimizations options are you using (I suggest -O3)? Also, perhaps you can try --enable-arm4-asm just in case. I've had the encoder running in real-time on a chip that's at least twice slower than yours with the settings you're using. Jean-Marc Le jeudi 15 septembre 2005 ? 16:23 -0400, Eduardo Bezerra a

...3 minutes it was the opposite. I have also another problem that is that sometimes the zap interface is unable o recognize the Dtmf digits (that are transmitted as mangled dtmf digits to another connected phone). Both of the above problems create to me suspects that a problem with the alaw and ulaw codifications is present into the code and that alaw saved files are played to ulaw equipment unmodified (whitout changing the format on the fly). Specifically I have tested to register an alaw file and then the IpPhone and the capi interface do hear well while the Zap interface hears badly, while if I do regist...

Dear all - Cody and Bert have some amusing points. The problems with R that Cody states are no different than those that any organization has with any programming work. Period. We've mostly solved them through appropriate approaches, addressing through quality management, some of the issues raised by Cody with respect to 3-rd party packages, etc. Quality Management != Absolute

> -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Chris > Lattner via llvm-dev > Sent: Thursday, May 05, 2016 4:36 PM > To: Renato Golin > Cc: llvm-dev > Subject: Re: [llvm-dev] Resuming the discussion of establishing an LLVM > code of conduct > > On May 5, 2016, at 4:02 PM, Renato Golin <renato.golin at

Folks, I'm trying to rationalize about optimization levels and maybe we should come up with a document like this: http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html Though, I remember a discussion a few months ago, and some people recommended we had names, rather than numbers, to dissociate the idea that 3 is better than 2. Regardless, would be good to have some guidelines on what goes