Are you using true OO (late binding)? Then it might be the vtables.
So far, we don't have a C++ maintainer for GCC/avr-libc, and thus
nobody ever bothered to teach GCC to place them into flash ROM rather
than RAM.
Joerg,
I think you may have nailed it there - assuming 2-byte function pointers in the vtables, 56 bytes sounds about right for the number of virtuals. Maybe I'll get off my lazy and change the class into a table of function pointers. I suppose someone could point me to the approximate location where you specify in the gcc source that the vtables go in rom, probably over my head to fix it, though.
Steve
_______________________________________________ AVR-chat mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-chat
