c++ code that egcs kills ...

Mike Stump mrs@wrs.com
Fri Aug 21 18:10:00 GMT 1998

> From: hjl@innovix.com (H.J. Lu)
> To: egcs-bugs@cygnus.com
> Date: Fri, 21 Aug 1998 10:01:34 -0700 (PDT)

> What is the unfinished part of the thunks implemantation?

The below.

> The only thing I can find is that expand_indirect_vtbls_init () in
> search.c has

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

> If the dynamic thunks is working, will that bug be fixed?


> Do we need a new thunks implemantation to fix it?

It's more vbase related than thunk related; Jason talks of a new way
to organize vbases, that is one way to fix it.  Implementation of
dynamic thunks would also do it.

> If the dynamic thunks is not implemanted and it does generate
> incorrect codes, why doesn't egcs issue a warning to user?

A warning isn't realistic I feel.  You would have to warn about _any_
vbase code.  This is like saying, sorry, we don't know how to code a
compiler, and we will bite you if you try and use this sucker...

I'd rather just turn off thunks than do a warning.

More information about the Gcc-bugs mailing list