This is the mail archive of the newlib@sourceware.org mailing list for the newlib 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: Using vector in setjmp.h for SPU.

From: trevor_smigiel at playstation dot sony dot com
To: jschopp <jschopp at austin dot ibm dot com>
Cc: newlib at sources dot redhat dot com, asayama at sm dot sony dot co dot jp
Date: Thu, 14 Dec 2006 14:11:07 -0800
Subject: Re: Using vector in setjmp.h for SPU.
References: <20061121024543.GC13699@playstation.sony.com> <20061214200702.GM7501@playstation.sony.com> <4581B8BA.8010501@austin.ibm.com>

Just vector doesn't work by default with the FSF version of gcc.  I
encountered the problem while building the latest newlib with the
latest FSF gcc.

Trevor

* jschopp <jschopp@austin.ibm.com> [2006-12-14 12:55]:
> trevor_smigiel@playstation.sony.com wrote:
> >Joel,
> >
> >Can you change the use of "vector" to "__vector" in
> >libc/include/machine/setjmp.h
> >
> >Only __vector is defined by default.  vector is only defined
> >when spu_intrinsics.h is included.
> 
> In the version of the gcc compiler I'm using both vector and __vector work 
> equally well with or without includes.  This is the case with xlc as well.  
> I haven't used the new FSF compiler yet, could you confirm this is actually 
> the case with it.  If it is I'll send the patch momentarily.

Follow-Ups:
- Re: Using vector in setjmp.h for SPU.
  - From: jschopp

References:
- Building newlib SPU port with FSF gcc
  - From: trevor_smigiel
- Using vector in setjmp.h for SPU.
  - From: trevor_smigiel
- Re: Using vector in setjmp.h for SPU.
  - From: jschopp

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