Re: [VXWORKS PPC 2.95.3] Readme - info.

["Dave Korn" <davek-ml at ntlworld dot com>]

> >
> >   If there's ever a 2.95.4, I could clean these patches up and make them
fit
> > for inclusion.
>
> There won't be.  However, there will be a 3.0 and 3.1 and so on.
> Could you clean them up and make them suitable for inclusion in 3.1?
>
> They probably aren't suitable for inclusion into GCC 3.0, because it's
> now in code slush, but they should be reviewed for the mainline CVS
> before going into any release branches.

      Hi Geoff,

   Once I've got my release stable, I'll look into this, but I'm not 100%
sure whether it will work or make sense.

  The ABI change is a big stumbling block.  In VxWorks, the C runtime, C++
support and STL libs are all part of the OS, and applications are
dynamically linked to them at load time.  So I'd have a nasty choice to make
between fixing the libstdc++ port for vxworks, and hoping that it replaced
all the OS functions in a compatible fashion; or providing a whole load of
wrapper functions to map the new name mangling onto the old.

  And god knows what I'd do about the different layouts of vtables and what
might happen when an OS routine tries to throw an exception back up to user
code.

  I'd be very interested if you or anyone else have any bright ideas how to
handle this problem; it's a shame, because I like the sound of 3.0, but it
may or may not be possible to make it work.

        DaveK