Re: c++ code that egcs kills ...

["Glenn W. Bach" <glenn at dodgson dot wonderland dot caltech dot edu>]

> 	if (flag_vtable_thunks)
> 	  {
> 	    /* We don't have dynamic thunks yet!
> 	       So for now, just fail silently.  */
> 	  }

That's scary!  Most users have never even heard of a thunk, so a silent
failure means that they will get incorrect code and never know why it
subsequently crashes.

> I believe this is a known problem in the vtable-thunks implementation.
> You may work around it by rebuilding libstdc++ with -fno-vtable-thunks 
> and compiling any C++ program with -fno-vtable-thunks.

When it is the compiler that is at fault, it is unacceptable for a widely
distributed library to require a custom version of a standard library like
libstdc++ .

> My preference was for people to finish off the implementation of
> thunks, and then if they are a codegen win, to default all
> architectures over to thunks.

I agree.  Either put in a fully functional feature or don't put it in at
all.

Glenn