This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc 3.1.1 eh_frame and global constructors for embedded platforms ie no start files


Ken Faiczak <kfaiczak@SANDVINE.com> writes:

> I'd be more than happy to take a crack at the 3.4 stuff, we are using ELF.

Cool.  See my response to your other message, shortly.

> However I need to get this other stuff working in the meantime, as I
> need to get mips64 support that is lacking in 3.0.3 and can't really
> wait 8 months.

I think that adding

#undef DEFAULT_USE_WEAK
#define DEFAULT_USE_WEAK 0
#undef TARGET_ASM_OUTPUT_CONSTRUCTOR
#undef TARGET_ASM_OUTPUT_DESTRUCTOR

to your config/mips/vxworks.h will get you past your current hurdle.

Also, snarf gthr-vxworks.h, config/vxlib.c, and
contrib/gthr_supp_vxw_5x.c from the basic-improvements branch.  They
should slot into earlier versions of 3.x without trouble.  (except
you'll need to add a dummy __gthread_key_dtor function).

> I'd really like to get rid of the munch script and use the linker
> properly to get this done so we can use 3.2 and 3.3 as they become
> available.

Unfortunately I do not believe it to be possible to use proper
.ctors/.dtors sections with any released version of VxWorks.  If you
can figure out how I would be delighted to hear your suggestions.

Using collect2 instead of munch ought to be possible; again,
suggestions for technique are welcome.

zw


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]