[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] fdevopen() uses calloc?
|
From: |
Joerg Wunsch |
|
Subject: |
Re: [avr-gcc-list] fdevopen() uses calloc? |
|
Date: |
Wed, 21 Jan 2004 17:19:45 +0100 (MET) |
"J.C. Wren" <address@hidden> wrote:
> Collectively, malloc(), calloc() and free() use around 1K, which is
> 6.25% of the code space on a Mega16. It also consumes 8 or so bytes
> of SRAM.
If you just implement your own versions that give out blocks from a
predefined buffer in SRAM, you should get away with less than 100
bytes of code. I think that ought to be at least a useful workaround.
>>I could provide a #define for the sizeof(struct __file) in <stdio.h>
>>if people found that to be useful.
> This could be useful.
OK, I'll do that. I'll only have to find a way first that guarantees
the entire compilation of avr-libc fails if the actual size and this
#define are out of sync.
--
J"org Wunsch Unix support engineer
address@hidden http://www.interface-systems.de/~j/
- [avr-gcc-list] power on mega 103, nurdin, 2004/01/20
- Re: [avr-gcc-list] power on mega 103, Joerg Wunsch, 2004/01/21
- [avr-gcc-list] Why no pgm_read_long() / pgm_read_long_far()?, J.C. Wren, 2004/01/21
- Re: [avr-gcc-list] fdevopen() uses calloc?, E. Weddington, 2004/01/21
- Re: [avr-gcc-list] fdevopen() uses calloc?, J.C. Wren, 2004/01/21
- Re: [avr-gcc-list] fdevopen() uses calloc?, Joerg Wunsch, 2004/01/21
- Re: [avr-gcc-list] fdevopen() uses calloc?, Rod Moffitt, 2004/01/22
- Re: [avr-gcc-list] Why no pgm_read_long() / pgm_read_long_far()?, E. Weddington, 2004/01/21
Re: [avr-gcc-list] power on mega 103, nurdin, 2004/01/23