adding mips-*-vxworks support to 3.4 -in basic-improvements branch

[Ken Faiczak <kfaiczak at SANDVINE dot com>]

okay I have the 3.4 source from cvs,
I'm not that familiar with how all this configure stuff works, mostly just
from trial and error
and probably not doing it sematically right at this time in getting 3.0.3
aqnd 3.1.1 working

I notice the mips-wrs-vxworks target is now gone from config.gcc
this is the target we currently use

I assume there should be a mips-*-vxworks
which would be the same

I want to be able to generate a lot of multilib variations for this
ie. isa       mips3/mips4/mips64
    endian    el/eb
    abi       n32/o64

I think this would suffice for most mips,vxworks targets today
anyway if I get it setup for these the others are trivial to add
(not sure if the other ABI are required, some may require o32
 we use o64, would like to use n32 or one of the eabi's if I knew what they
were
 and there was some advantage to them)

at least these are required.
I have this working on 3.1.1 (sans cons/except)
------------------------------------------
config.gcc:
mips-wrs-vxworks)
 tm_file="mips/vxworks.h"
 tmake_file=mips/t-elf
 gas=yes
 gnu_ld=yes
 extra_parts="crtbegin.o crtend.o"
 thread_file="vxworks"
 ;;

config/mips/t-elf:
I modified the t-elf file to create the various multilib options
 I created a t-vxworks file for this as well but have not used it yet
  not sure what the best way is to do that, I think I just change the
tmake_file??

config/mips/vxworks.h: (not sure if these includes should just have been
done in the tm_file= line
got rid of the DEFAULT stuff
and 
include "mips/elf.h"
include "abi64.h"

--------------------------------

Anyway I don't want to just blunder through it and do it wrong,
is there an example of something similar I could follow.

ken




-----Original Message-----
From: Zack Weinberg [mailto:zack@codesourcery.com]
Sent: Thursday, November 14, 2002 7:01 PM
To: Ken Faiczak
Cc: 'gcc@gnu.org'
Subject: Re: gcc 3.1.1 eh_frame and global constructors for embedded
platforms ie no start files


Ken Faiczak <kfaiczak@SANDVINE.com> writes:

> We are currently using gcc 3.0.3 for mips-wrs-vxworks
> and trying to upgrade to 3.1.1 & 3.2

Don't bother trying to use either 3.1.1 or 3.2 with VxWorks.  The
configurations are totally broken.

If you are brave, you can update all the way to the
"gcc-3_4-basic-improvements-branch", and write us a
config/mips/vxworks.h for that.  I'll be happy to help you with this.
However, be warned that this is an unstable development branch; it's
not going to be released for at least eight months.  Also, we're not
interested in supporting non-ELF VxWorks (i.e. 5.4 and earlier) in
current GCC.

zw