search for: vdsp

Robin Getz a ?crit : >> As I told you, bank is a reserved keyword in Analog Devices compiler for >> Blackfin architecture. > > This seems lame, and maybe you need to change the header files inside VDSP++. > (This is pretty common for VDSP users to do when name space clashes occur > with open source software). > > Poking at the VDSP docs, says that it uses bank() rather than the industry > standard __attribute(section("foo")) - so you can't change that with a heade...

...? Critical code ? Input samples ? Code-books ? Can we pre-allocate internal buffers heavily used by the encoder ? I'm also trying to compile Speex with asm optimizations. But it's targetted for GCC... I went through the archives, and found some entry-points to port asm-constraints to the VDSP compiler. But I'm facing the problem of 'dynamic' labels for loops. I don't know if Michael Shatz has completed the port... If you're reading this. Would you share your files ? Jean-Marc, I don't want to come back on the debate, but I think you should include the VDSP arch...

...Do I need to initialize extra things ? See myspeex.c code. It's pretty simple. I noticed a very interesting thing: the echo-cancellation totally removes this problem !!! How can I help you debug this thing ? My platform is Blackfin fixed-point on visual DSP. I can't use the debug-out on VDSP (too slow), but my custom-board has IP and RS232 interfaces which could help. > Depending on whether you're using all the > bit-rates, you might want to put only some of the codebooks > in SRAM (if you tell me what bit-rate, I can tell you which > codebooks you need). > About...

Hi Michael, hi all, is there any news from this topic? http://lists.xiph.org/pipermail/speex-dev/2008-February/006561.html Michael tried to translate the GNU constraints to VDSP, but it shows no improvement. Is it only for performance or are there other things? I also had a look in the ADI-Speex in their SDK, but it is an older version and the BFIN_ASM does not work. There are no other options, or ASM translations. Is the VDSP-Compiler so good, that performance or other...

> So, I did following changes: > In every loop I remove %= (In Vis.DSP Help I didn't find such sign) > And loop become able to compile. Let me know if you think of something that would work in both gcc and VDSP. > With parallel issues I found several interesting things: > > 1) > "A0 -= R1.L*R0.H (IS), A1 -= R1.L*R0.L (M,IS) || R0 = [%1++];\n\t" > //doesn't compile > It can be compiled in that way: > "A1 -= R1.L*R0.L (M), A0 -= R1.L*R0.H (IS) || R0 = [%1++];\n\t&qu...

...ns are identical. > > Did you change something in the API ? > Do I need to initialize extra things ? Can you test with testenc just to make sure? The only thing I can think of is that some of the assembly that got written/modified between beta1 and beta2 broke it (maybe it's just for VDSP). Could you try doing a bisection in svn and pinpoint which commit is causing problems? > I noticed a very interesting thing: the echo-cancellation totally removes > this problem !!! You mean that the codec works if you add the echo canceller??? Could be a memory issue... > How can I he...

Hi Jean-Marc, As I told you, bank is a reserved keyword in Analog Devices compiler for Blackfin architecture. So we need to change the variables named bank to something else. Here's a patch that changes bank to bnk in the 3 concerned files. (Hope the format is OK) About my previous problems with the Blackfin: -> strange block repetition that could be cancelled by the AEC I was busy

...e not so minor >> problem - the library is slow. However when I'm trying to compiler with >> inline assembler the compilation fails. It looks like ADI Blackfin assembler >> is not compatible with gas. > >There are a few things: > - gcc/gas can do some things that VDSP is not capable of > - the syntax is different for inline assembly (constraints are different). > - assembler directives are different > - compiler pragmas are different > - gcc supports an additional ABI. > >There are more details at: >http://docs.blackfin.uclinux.org/doku.php?...

...the codebooks in SRAM (if you tell me what bit-rate, I can tell you which codebooks you need). About code, it could be a bit more tricky and I don't know whether everything can fit into SRAM. > Jean-Marc, I don't want to come back on the debate, > but I think you should include the VDSP architecture. What do you mean by "the VDSP architecture"? > (there is also a problem with variables named "bank" > which is a compiler keyword...) You don't even need that part of the code actually. Try getting the git/svn version where I actually did a split into...

Hi I'm trying to integrate your speex codec on our custom Blackfin board and without uCLinux. I am using ADI-supplied VisualDSP++ IDE and corresponding toolchain. My question is: Is there anybody who ported speex with enabled BFIN_ASM to VisualDSP++ ? Best Regards, Stefan Voss -------------- next part -------------- An HTML attachment was scrubbed... URL:

...VisualDSP++ IDE and corresponding >> toolchain. My question is: Is there anybody who ported speex with enabled >> BFIN_ASM to VisualDSP++ ? > > Nope - two choices: > - check out using gcc for your entire project > - use the old version of speex that is avaliable as a VDSP download. > http://www.analog.com/processors/platforms/sdk.html Hi Stefan, if you look at the mailing-list archives, you can see there was a guy Michael Shatz who tried it, but no news... I'm currently 'translating' GNU assembly constraints to VDSP. I'm far from finished, b...

...ne that's easier on DSPs, right? Yes exactly, plus a little explanation in comments. I really have no idea of the performance difference on x86. But I think gcc/msvc can unroll. Up to you. Anyway I can OVERRIDE_INNER_PRODUCT_SINGLE. Talking about performance (still using generic version with VDSP compiler): 1. I got a pretty good boost by using a scratch buffer in SRAM. 2. Wideband Encode+Decode takes 79.1 + 7.2 MIPS on my BF536 400/133 Mhz 3. Profiler says: vq_nbest 33.05% vq_nbest_sign 11.12% filter_mem16 4.14% inner_prod 4.07% ii...

...n the >future). > >http://forms.analog.com/Form_Pages/support/dsp/dspSupport.asp > >Last time I asked, they said it was not possible, and mumbled something about >gcc accepting illegal operands. (which we are not - gcc just allows more >general purpose register allocation than VDSP does, so the inline puts more >register pressure on the VDSP than on gcc). > >-Robin Not sure that the people at ADI are the best for the job. And not only because of lack good will on their part. Mechanical fix of the syntax is probably far from optimal. You want to test _and profile_...

Hi Jean-Marc I'm trying to integrate your speex codec on our custom Blackfin board. The board is not uCLinux compatible and there is no chance that it will ever be. I am using ADI-supplied VisualDSP++ IDE and corresponding toolchain. As long as I am compiling "C"-only version of the library everything is fine. VisualDSP++ produces working library. There is only one not so minor

...etter way to do it. It is essentially what you'd do to make longer vector dot products such as your 40-160 sample dots work quickly. Do them as 4 parallel partial vector dots and then sum across the vector containing the four results. On MacOS X, there is also a hand tuned dot product in vecLib/vDSP.h, dotpr(), if you'd rather just call that. Personally, I don't think much of PNI. The complex arithmetic stuff they added sets you up for a lot of permute overhead that is inefficient -- especially on a processor that is already weak on permute. In my opinion, its a big ISA trojan horse....

Stephane Lesage a ?crit : > > Hi Jean-Marc, > > As I told you, bank is a reserved keyword in Analog Devices compiler for > Blackfin architecture. > So we need to change the variables named bank to something else. You mean the VDSP compiler that people seem to have mostly replaced with gcc? > Here's a patch that changes bank to bnk in the 3 concerned files. > (Hope the format is OK) The format's fine, but I don't exactly like having to change all the names just because some compiler somewhere thought it wa...

Jean-Marc Valin a ?crit : > Stephane Lesage a ?crit : > The format's fine, but I don't exactly like having to change all the > names just because some compiler somewhere thought it was a good idea to > redefine keywords. How about you just compile with -Dbank=bnk ? Yep it's working. What about including these 3 lines in arch.h ? #ifdef __ADSPBLACKFIN__ #define bank bnk

Hi, I'm using a Windows development component which uses vorbis.dll, ogg.dll, vorbisenc.dll for encoding a file. When finishing a recording, the component runs these functions... ogg_stream_clear(OggSS); vorbis_block_clear(VBlock); vorbis_dsp_clear(Vdsp); vorbis_comment_clear(VComm); vorbis_info_clear(VInfo); I'm occasionally receiving a hang in the function vorbis_info_clear(vinfo) which goes to 100% CPU indefinitely. I've tried different compiles of vorbis.dll without success. I've checked the VInfo structure has valid inf...

...> > It involves a different ASM implementation. > > - intruction syntax is the same > > - some constraints are different > > How different? Not so much, it's easy to handle, but would require specific syntax. > > - 'dynamic' labels are not available on VDSP (when you use > an inline > > several times, the gcc compiler can do some kind of incrementation) > > What would you use instead? hehe, that's where I have trouble. No documentation on how to do this... I guess I will have to use PC-relative addressing-mode and compute the of...

> Please note that dot products of simple vector floats are usually > faster > in the scalar units. The add across and transfer to scalar is just too > expensive. Or do four at once, with some shuffling (which is basically free); almost the same code as a 4x4 matrix/vector multiply. <p>Segher --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: