Related articles |
---|
Parser Generators for Multiple Protocols in an Embedded Device nou.dadoun@polycom.com (2002-04-23) |
Re: Parser Generators for Multiple Protocols in an Embedded Device k.prasad@attbi.com (Kamal R. Prasad) (2002-04-29) |
Re: Parser Generators for Multiple Protocols in an Embedded Device haberg@matematik.su.se (2002-05-01) |
Re: Parser Generators for Multiple Protocols in an Embedded Device iddw@hotmail.com (2002-05-03) |
Re: Parser Generators for Multiple Protocols in an Embedded Device joachim.durchholz@munich.netsurf.de (Joachim Durchholz) (2002-05-03) |
Re: Parser Generators for Multiple Protocols in an Embedded Device k.prasad@attbi.com (Kamal R. Prasad) (2002-05-04) |
From: | Joachim Durchholz <joachim.durchholz@munich.netsurf.de> |
Newsgroups: | comp.compilers,comp.lang.misc |
Date: | 3 May 2002 16:04:29 -0400 |
Organization: | Compilers Central |
References: | 02-04-133 02-04-154 02-05-006 |
Keywords: | design, storage |
Posted-Date: | 03 May 2002 16:04:29 EDT |
Hans Aberg wrote:
> It means that also embedded programming, as memory becomes plenty,
> will make use of high level programming techniques.
Memory in embedded devices has never been plenty, and I doubt it ever will.
There are two limiting factors: component price and power consumption.
As an example for limitations in both, take digital
wristwatches. Saving ten cent per watch in production will make the
watch cheaper by two to ten dollars. And a smaller RAM means less
frequent battery changes, which watch owners usually prefer. (In fact
a watch that has a battery life of ten years instead of the one year
that's normal today would have a market. Meaning even less RAM, or
even the production of an specialized chip with an extra-little RAM to
further tailor down power consumption.)
So, in summary, it still pays off to have compilers that can optimize
for space. Of course, the definition of "scarce" memory will vary
over time. Future embedded controllers will have more memory, on the
order of magnitudes. But it will always be constrained to the minimum
that's considered viable (and probably a little less).
Regards,
Joachim
Return to the
comp.compilers page.
Search the
comp.compilers archives again.