🚀 go-pugleaf

vanpraet@imec.be (Johan Van Praet) writes:


>I am writing a report on different approaches to generate code for a
>DSP processor and would like to hear some opinions of the net-people
>about this.

>- Which method do you use to write code ?

All my DSP code is 100% assembler, but I often prototype algorithms
in MATLAB on a PC to get the *algorithm* right, before diving into
coding for speed on the DSP.

DSP assembly language is such that it is relatively easy to write good,
readable code (main experience is with DSP32c and ADSP21xx). I find that
a compiler really does not make coding that much easier, particularly if
the assembler supports macros etc. Direct assembly language coding
also allows me to use tricks with the pipeline, special addressing modes (eg
bit-reversed, circular buffers), zero-overhead loops and so on, squeezing
as much useful work out of the processor as possible. (Most of my work
is in audio processing)

DSP chips are designed to be fast, and to slow them down with compiled code
seems daft, particularly in real-time applications. Obviously development
time (and hence cost) is an issue, but I can write DSP code as good as any 
compiler, just not quite as quick...:-)

Christopher-- 
 ==============================================================================
 Christopher Hicks    |    If it doesn't fit...
 cmh@uk.ac.cam.eng    |                        ...you need a bigger hammer.
 ==============================================================================
--
 ==============================================================================
 Christopher Hicks    |    If it doesn't fit...
 cmh@uk.ac.cam.eng    |                        ...you need a bigger hammer.
 ==============================================================================