All you anti-C++ guys -- just hold it in. You won't convince me and I won't convince you.
I made a comment in Pozz's thread on avoiding malloc that I had tried C++ on a processor with 8k of memory and couldn't make it fit.
The experiment, as I remember it, was to write a basic hollow shell, build it in C and in C++, and see that it used something like 6k more flash with C++ than with C (it may not be 6k -- it was a lot with respect to 8k, and not much with respect to 64k).
It was the gnu toolchain with newlib (it's the arm-none-eabi toolchain).
In theory, if you're thrifty with your C++, you shouldn't pull in any more junk than you would in C. Obviously it's different in practice.
Has anyone managed to really trim this down? It's kind of immaterial anyway, because if you're doing something that will reasonably fit into8kB of flash then you don't need all of the features of C++ that make it easier to author big programs. But I'm curious.