Re: C++ pure virtual base class memory consumption

[fueb <fueb at gmx dot net>]

Sebastian Huber-4 wrote:
> 
> Are you sure this code is from Newlib and not GCC?
> 

I think the code is being inserted by GCC and in turn many things from
newlib get linked in. 
../arm-none-eabi/lib/thumb2\libstdc++.a(pure.o)
../arm-none-eabi/lib/thumb2\libstdc++.a(eh_terminate.o)
../arm-none-eabi/lib/thumb2\libstdc++.a(eh_call.o)
../arm-none-eabi/lib/thumb2\libstdc++.a(eh_exception.o)

and may other things I cannot post here since the mapfile is quite large. 


Sebastian Huber-4 wrote:
> 
> I suppose this is due to the abort handler with pretty printing pulled in
> by a 
> pure virtual function.  You should look at the map file of the linker. 
> See also
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43852
> 

Newlib's printf is already in the application, this doesn't blow up the code
so much, like the 
pure virtual function does. I've read the bug details but I am not very
familiar with newlib. 
Does it mean I have to rebuild my newlib installation with the mentioned
compiler flags?

-- 
View this message in context: http://old.nabble.com/C%2B%2B-pure-virtual-base-class-memory-consumption-tp34325972p34330808.html
Sent from the Sourceware - newlib list mailing list archive at Nabble.com.