C code .vs. Assembly code for Microcontrollers/DSPs ?

ravindra@hal.com (Ravindra Divekar)
1 Mar 1996 13:52:30 -0500

          From comp.compilers
Related articles
C code .vs. Assembly code for Microcontrollers/DSPs ? ravindra@hal.com (1996-03-01)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? dstarr@pop-3.std.com (David J. Starr) (1996-03-03)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? mwilliam@duncan.cs.utk.edu (1996-03-03)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? eyal@dsp.co.il (Eyal Ben-Avraham) (1996-03-03)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? jens.hansson@mailbox.swipnet.se (1996-03-03)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? torbenm@diku.dk (1996-03-04)
Re: C code .vs. Assembly code for Microcontrollers/DSPs ? andrew@memex.co.uk (Andrew Cruickshank) (1996-03-04)
[58 later articles]
| List of all articles for this month |
From: ravindra@hal.com (Ravindra Divekar)
Newsgroups: comp.arch,comp.realtime,comp.compilers,comp.lsi,comp.dsp
Date: 1 Mar 1996 13:52:30 -0500
Organization: HaL Computer Systems, Inc.
Keywords: C, performance, question

I've heard people say so many times, that hand-crafted (assembly) code
is more compact than compiled C code for microcontrollers or DSPs.


So where is the problem?


Is it a limitation of existing compiler technology (so much for the
optimization hype) ?


Is it the choice of high level language i.e. C/C++ that matters ?


Is it the nature of application (scientific/real-time/control/float.pt)
that creates porting problems?


Or is it just the architectural features of typical microcontrollers that
make things difficult ?


thanx....Ravindra.
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.