Related articles |
---|
Comparing Compilers ganesh.pagade@gmail.com (G P) (2004-11-06) |
Re: Comparing Compilers touati@prism.uvsq.fr (TOUATI Sid) (2004-11-14) |
Re: Comparing Compilers ganesh.pagade@gmail.com (G P) (2004-11-14) |
Re: Comparing Compilers ganesh.pagade@gmail.com (G P) (2004-11-17) |
Re: Comparing Compilers pohjalai@cc.helsinki.fi (A Pietu Pohjalainen) (2004-11-17) |
Re: Comparing Compilers rweaver@ix.netcom.com (Dick Weaver) (2004-11-17) |
Re: Comparing Compilers touati@prism.uvsq.fr (TOUATI Sid) (2004-11-28) |
Re: Comparing Compilers henry@spsystems.net (2004-12-13) |
From: | A Pietu Pohjalainen <pohjalai@cc.helsinki.fi> |
Newsgroups: | comp.compilers |
Date: | 17 Nov 2004 11:30:29 -0500 |
Organization: | University of Helsinki |
References: | 04-11-015 04-11-033 |
Keywords: | performance, practice |
Posted-Date: | 17 Nov 2004 11:30:29 EST |
TOUATI Sid <touati@prism.uvsq.fr> wrote:
> The same remark for code size : who cares if you generate a code of 4.9
> Ko instead of 4 ko. However, I think that many people would care if you
> generate 4.9 Go instead of 4 Go.
People compiling Java to mobile phones (J2ME) actually do care on
savings of one kilobyte in the size of the compiled code. This is
because the phone manufacturers, especially on the low-end models
limit the maximum size of the deployable program to e.g. 30kB.
I would believe that the situation is similar in many embedded systems.
br,
Pietu Pohjalainen
Return to the
comp.compilers page.
Search the
comp.compilers archives again.