Question about global object constructors, VxWorks, and GCC 2.95(fwd)

Luke Diamand lgd@virata.com
Thu Dec 16 04:31:00 GMT 1999


ftp://ftp.virata.com/pub/unsupported/gnu

HTH!
Luke Diamand

Bryan Ogawa wrote:
> 
> On Tue, 16 Nov 1999, Luke Diamand wrote:
> 
> Luke,
> 
> I was wondering if you happened to have that code for globalize-symbol
> handy?
> 
> > The problem is that gcc 2.95 makes the ctor objects local.
> >
> > Here's some code compiled with gcc 2.95.1:
> >
> > 00000068 t L2
> > 00000048 t L5
> > 00000044 t L8
> > 0000006c t __GLOBAL_.I.x_
> > 0000004c t ___1X
> > 00000000 t ___static_initialization_and_destruction_0
> > 00000000 B _x_
> >          U _x__Fv
> >
> > And here's the same code compiled with gcc 2.8.1:
> >
> > 0000003c t .L1
> > 0000001c t .L6
> > 00000018 t .L7
> > 00000000 T __GLOBAL_$I$x_
> > 00000020 t ___1X
> > 00000000 B _x_
> >          U _x__Fv
> >
> > We've not had this precise problem with VxWorks, but we do have an
> > analgous problem, which we have solved by patching objcopy to give it a
> > --globalize-symbol option.
> >
> > If anyone's interested, I'll pop it on an ftp site somewhere. Working
> > out what to do with collect2 is probably the right thing to do, though
> > ;-(
> 
> Thanks,
> 
> --
> Bryan K. Ogawa  <bogawa@vovida.com>  http://www.vovida.com/

-- 
Virata http://www.virata.com
Cambridge
Tel: +44 1223 566919      Fax: +44 1223 566915

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com



More information about the crossgcc mailing list