search for: shatz

...eex 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 ? > > > > Best regards. >

> -----Original Message----- > From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] > Sent: Thursday, November 22, 2007 12:16 AM > To: St?phane Lesage > Subject: Re: [Speex-dev] Blackfin port on Visual DSP, Michael Shatz ? > > (en passant, tu es francophone?) oui, fran?ais, travaillant pour une soci?t? suisse ;-) > > St?phane Lesage a ?crit : > > It's not easy for me to use testenc. > > (I have no file-system and limited memory) > > Fair enough. Well, actually, I found-out th...

...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 architecture. (there is also a problem with variables named "bank" which is a compiler keyword...) Best re...

> No I didn't know this macro. > > According to the sources, I understand it's destined to compilers supporting > run-time size for local arrays on the stack. > > But this is not documented (API or user manual), and does not appear in any > header file. > It should appear at least in arch.h, commented and defaulting to #undef... Actually, it's meant to be

> -----Original Message----- > From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] > Sent: Wednesday, October 17, 2007 1:56 AM > To: St?phane Lesage > Cc: speex-dev@xiph.org > Subject: Re: [Speex-dev] Blackfin port on Visual DSP, Michael Shatz ? Salut Jean-Marc, After 1 month busy on other projects, I can finally answer you: > Some things to check. Do you compile with VAR_ARRAYS? If not, > you can probably reduce the size of the managed stack. In > terms of data RAM, everything should fit into SRAM easily. No I didn't...

...looks like ADI Blackfin assembler is not compatible with gas. Supposedly you are aware of the problem since amongst Blackfin developers VisualDSP++ toolchain is the most popular by far. Actually I know noone who use gnu toolchain. Could you suggest a solution for my problem? Best Regards, Michael Shatz -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/speex-dev/attachments/20070613/3a51f0ae/attachment.html

-----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Thursday, June 14, 2007 11:17 PM To: Michael Shatz Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Blackfin inline assembler and VisualDSP++ toolchain Michael Shatz a ?crit : >>> Actually, you're the first I know using the VisualDSP++ toolchain >>> :-) >> >> I guess that's because speex has pretty big memory...

-----Original Message----- From: Robin Getz [mailto:rgetz@blackfin.uclinux.org] Sent: Saturday, June 16, 2007 12:11 AM To: Michael Shatz Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Blackfin inline assembler and VisualDSP++ toolchain >On Wed 13 Jun 2007 12:37, Michael Shatz pondered: >> >> Hi Jean-Marc >> >> I'm trying to integrate your speex codec on our custom Blackfin board. The >> boa...

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:

...; 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, but first attempts show no improvement over the C compiler. This is rather strange and would suggest memory bandwith limitation rather than code efficiency. I will in...

>-----Original Message----- >From: Robin Getz [mailto:rgetz@blackfin.uclinux.org] >Sent: Tuesday, June 19, 2007 9:35 PM > > >On Tue 19 Jun 2007 13:00, Michael Shatz pondered: >> Robin Getz wrote: >> >I never met any hardware that gcc could not run code on. toolchains have >> >nothing do with embedded OSes. >> >> That's true. Add some postprocessing, program binary into flash and >> code would run. But you likel...

> >Actually, you're the first I know using the VisualDSP++ toolchain :-) > I guess that's because speex has pretty big memory footprint. So developers that integrate speex tend to have plenty of RAM and once one has plenty of RAM he could install biggish OS. And between biggish OSes for Blackfin the most popular choice is uCLinux. And ucLinux works best with gnu tools. Something

-----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Tuesday, June 19, 2007 6:38 PM To: Michael Shatz Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Blackfin inline assembler and VisualDSP++ toolchain >> Yes, data footprint in the new version is quite manageable. Still I would >> wish better documentation for speex_alloc_scratch(). > >I'll be waiting for your patch :-) I...

...; Lennert Buytenhek <kernel@wantstofly.org> Lennox Wu <lennox.wu@gmail.com> Leo Alterman <lalterman@nicira.com> Leo Song <liangs@marvell.com> Leo Yan <leoy@marvell.com> Leon Romanovsky <leon@leon.nu> Leonid Isaev <lisaev@umail.iu.edu> Leonid Shatz <leonid.shatz@ravellosystems.com> Leonid Yegoshin <yegoshin@mips.com> Ley Foon Tan <lftan@altera.com> Li Dongyang <Jerry87905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <l...

...; Lennert Buytenhek <kernel@wantstofly.org> Lennox Wu <lennox.wu@gmail.com> Leo Alterman <lalterman@nicira.com> Leo Song <liangs@marvell.com> Leo Yan <leoy@marvell.com> Leon Romanovsky <leon@leon.nu> Leonid Isaev <lisaev@umail.iu.edu> Leonid Shatz <leonid.shatz@ravellosystems.com> Leonid Yegoshin <yegoshin@mips.com> Ley Foon Tan <lftan@altera.com> Li Dongyang <Jerry87905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <l...

...; Lennert Buytenhek <kernel@wantstofly.org> Lennox Wu <lennox.wu@gmail.com> Leo Alterman <lalterman@nicira.com> Leo Song <liangs@marvell.com> Leo Yan <leoy@marvell.com> Leon Romanovsky <leon@leon.nu> Leonid Isaev <lisaev@umail.iu.edu> Leonid Shatz <leonid.shatz@ravellosystems.com> Leonid Yegoshin <yegoshin@mips.com> Ley Foon Tan <lftan@altera.com> Li Dongyang <Jerry87905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <l...

...; Lennert Buytenhek <kernel@wantstofly.org> Lennox Wu <lennox.wu@gmail.com> Leo Alterman <lalterman@nicira.com> Leo Song <liangs@marvell.com> Leo Yan <leoy@marvell.com> Leon Romanovsky <leon@leon.nu> Leonid Isaev <lisaev@umail.iu.edu> Leonid Shatz <leonid.shatz@ravellosystems.com> Leonid Yegoshin <yegoshin@mips.com> Ley Foon Tan <lftan@altera.com> Li Dongyang <Jerry87905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <l...

...; Lennert Buytenhek <kernel@wantstofly.org> Lennox Wu <lennox.wu@gmail.com> Leo Alterman <lalterman@nicira.com> Leo Song <liangs@marvell.com> Leo Yan <leoy@marvell.com> Leon Romanovsky <leon@leon.nu> Leonid Isaev <lisaev@umail.iu.edu> Leonid Shatz <leonid.shatz@ravellosystems.com> Leonid Yegoshin <yegoshin@mips.com> Ley Foon Tan <lftan@altera.com> Li Dongyang <Jerry87905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com> Li Wang <wangli@kylinos.com.cn> Li Wei <l...

...; Lennert Buytenhek <kernel@wantstofly.org> Lennox Wu <lennox.wu@gmail.com> Leo Alterman <lalterman@nicira.com> Leo Song <liangs@marvell.com> Leo Yan <leoy@marvell.com> Leon Romanovsky <leon@leon.nu> Leonid Isaev <lisaev@umail.iu.edu> Leonid Shatz <leonid.shatz@ravellosystems.com> Leonid Yegoshin <Leonid.Yegoshin@imgtec.com> Leonid Yegoshin <yegoshin@mips.com> Ley Foon Tan <lftan@altera.com> Li Dongyang <Jerry87905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com>...

...; Lennert Buytenhek <kernel@wantstofly.org> Lennox Wu <lennox.wu@gmail.com> Leo Alterman <lalterman@nicira.com> Leo Song <liangs@marvell.com> Leo Yan <leoy@marvell.com> Leon Romanovsky <leon@leon.nu> Leonid Isaev <lisaev@umail.iu.edu> Leonid Shatz <leonid.shatz@ravellosystems.com> Leonid Yegoshin <Leonid.Yegoshin@imgtec.com> Leonid Yegoshin <yegoshin@mips.com> Ley Foon Tan <lftan@altera.com> Li Dongyang <Jerry87905@gmail.com> Li Fei <fei.li@intel.com> Li RongQing <roy.qing.li@gmail.com>...