This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


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: iWMMXt Linux EABI cross toolchain


--- Khem Raj <khem@mvista.com> wrote:

> Steven Newbury said the following on 03/03/2006 12:11 PM:
> > --- Khem Raj <khem@mvista.com> wrote:
> >   
> >> As evidents from Paul's IWMMXt ABI is kind of intermediate thing which 
> >> got started in same direction to refine ABI requirements but then was 
> >> converted into a more detailed work to define ARM EABI therefore EABI is 
> >> complete so I would suggest youto use EABI instead.
> >>     
> > So if I don't specify an ABI but use --with-cpu=iwmmxt --with-arch=iwmmxt
> and
> > do as I am targeting arm-iwmmxt-linux-gnueabi it should do the right thing
> wrt
> > vectorizing etc?  
> it should.
> > Or should I select AAPCS?
> >   
> no
> > Is this also likely to fix my problem of missing forced-unwind when
> compiling
> > glibc??
> >   
> no that probably is because you enabled thread support and C++ support 
> into minimal gcc.
Yes I enabled thread support, not C++ though.  I couldn't get glibc to compile
without threads; see my earlier post in this thread.  So I'm stuck. :(

Maybe it's a bug in my glibc CVS pull stopping it building without threads?
I'll  try updating it...


Steve


		
___________________________________________________________ 
NEW Yahoo! Cars - sell your car and browse thousands of new and used cars online! http://uk.cars.yahoo.com/

--
For unsubscribe information see http://sourceware.org/lists.html#faq


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