[Let's move that out to avr-gcc-list instead, it's well on-topic there.] Rolf Magnus <[EMAIL PROTECTED]> wrote:
>> Oh, while you are at it, move the vtables out to ROM, please. :-) > I'd really love that. Would try it myself, but I guess it would > require a lot of hard work to dig into the g++ code for someone who > has never looked into it. I have no idea about it. I've got already enough AVR stuff at my hands, so I don't volunteer to become Mr. AVR-G++. ;-) Speaking about AVR-G++, I filed a GCC bug report yesterday: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28718 By comparision with my FreeBSD host's G++, it appears to be a feature they normally link libstdc++ and libm before any user-supplied libraries. As on the AVR, there is no libstdc++, libgcc is (ab)used instead. This causes really ``funny'' behaviour. In the simpler case, it just causes a lot of bloat to be added from libgcc.a (rather than the hand-tunded stuff from libm.a), and in the case where a user forced the floating-point printf library, it causes double definitions of external symbols. -- J"org Wunsch Unix support engineer [EMAIL PROTECTED] http://www.interface-systems.de/~j/ _______________________________________________ AVR-chat mailing list AVR-chat@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-chat _______________________________________________ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
