| |
On Sun, 15 Oct 2000, Paolo Masetti wrote:
> You can test memory left using the routine from Eddie:
>
> http://news.lugnet.com/robotics/rcx/legos/?n=1129
Excellent, thanks for the pointer.
> LegOS is already optimized for space. You can save some bytes changing
> config.h to exclude some features, but I think that the best place for
> optimizing is your own program...
Well, I was thinking along the lines of having gcc optimize my program for
space instead of speed. Of course, I'd be better off if *I* optimized for
space instead of speed, but it can't hurt to have the compiler working for
me, if it's possible.
--
"Say not, 'I have found the truth,' but rather, 'I have found a truth.'
"Say not, 'I have found the path of the soul.' Say rather, 'I have met the
soul walking upon my path.'" -- Khalil Gibran
Mike Ash - <http://www.mikeash.com/>, <mailto:mail@mikeash.com>
|
|
Message has 1 Reply:
 | | Re: Memory Usage
|
| (...) changing (...) place for (...) program for (...) optimized for (...) working for (...) I've further investigated and you can gain some more bytes compiling kernel (and your programs) with -Os option instead of -O2 (Makefile.common, COPT (...) (24 years ago, 15-Oct-00, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
| | Re: Memory Usage
|
| (...) itself in (...) allocate (...) annoying, (...) You can test memory left using the routine from Eddie: (URL) Anyway, my question is, how can I reduce memory usage? I think cutting (...) HOWTO, (...) that (...) a (...) in (...) process is (...) (...) (24 years ago, 15-Oct-00, to lugnet.robotics.rcx.legos)
|
6 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
