 | | 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)
| | | | | 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)
| | | | | 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)
| | | | | 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)
| | | | | Re: Memory Usage
|
| (...) Having written a few embedded-systems compilers, I must say that using floating point on an 8-bit chip like the H8 is generally considered crazy. The values eat memory, and the libraries drawn in can get really large (at least for a production (...) (23 years ago, 25-Mar-01, to lugnet.robotics.rcx.legos)
| |
