|
|
 | | 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
|
| (...) 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
|
| (...) 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)
| | | | | Memory Usage
|
| Well, I've gone and run out of memory with my RCX. It manifested itself in a task that refused to run, presumably because the OS couldn't allocate enough memory for its stack. Took a while to track down and was annoying, but it was my own fault for (...) (24 years ago, 14-Oct-00, to lugnet.robotics.rcx.legos)
| | | | | winlnp
|
| well, one page is still up... (URL) sure if anyone wants to pursue that or not (Yannis, if you are around, and need space to mirror your files, legOS.sourceforge.net is there for you ;) Luis ---...--- "It's clear to us that Microsoft isn't the (...) (24 years ago, 13-Oct-00, to lugnet.robotics.rcx.legos)
|
|
