| |
> > 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.
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 define), but we are speaking of
very few bytes.
Note that legos 0.2.4 was never tested with this option, AFAIK.
Bye,
Paolo.
---
Fett's Law: Never replicate a successful experiment.
|
|
Message has 1 Reply:
 | | Re: Memory Usage
|
| (...) Ok, thanks. I'll try everything else first, then try this if I get desperate. The main thing I hit a wall with was when I switched to floating-point, which increased my .lx filesize by about 2k, so if I go back to fixed-point, turn sound off (...) (24 years ago, 15-Oct-00, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
| | Re: Memory Usage
|
| (...) 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 (...) (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
|
|
|
|
