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: Implicit altivec vs. linux kernel build

From: Andrew Pinski <pinskia at physics dot uc dot edu>
To: David Edelsohn <dje at watson dot ibm dot com>
Cc: Paul Mackerras <paulus at samba dot org>, Geoff Keating <geoffk at geoffk dot org>, gcc at gcc dot gnu dot org, Alan Modra <amodra at bigpond dot net dot au>, Benjamin Herrenschmidt <benh at kernel dot crashing dot org>
Date: Sun, 27 Feb 2005 19:04:15 -0500
Subject: Re: Implicit altivec vs. linux kernel build
References: <1109545242.14992.234.camel@gaston> <200502272335.j1RNZDD27844@makai.watson.ibm.com> <653d1ad4308fa0e72f08252032f6c753@physics.uc.edu> <1109548140.15027.239.camel@gaston> <200502272356.j1RNuBD31238@makai.watson.ibm.com>

On Feb 27, 2005, at 6:56 PM, David Edelsohn wrote:

Benjamin Herrenschmidt writes:

Ben> Ok. What I need is -mcpu=power4 -maltivec

	Sorry, no.  -maltivec means generate Altivec code, not just enable
Altivec instructions and registers.  The above option is not different
than -mcpu=970.  There is no DWIM option.

He means for the one file which is used in the altivec situation so he could use -mcpu=power4 all over the place and just use -maltivec on that one file. Hopefully that clears up the issue here.

-- Pinski

References:
- Re: Implicit altivec vs. linux kernel build
  - From: Benjamin Herrenschmidt
- Re: Implicit altivec vs. linux kernel build
  - From: David Edelsohn
- Re: Implicit altivec vs. linux kernel build
  - From: Andrew Pinski
- Re: Implicit altivec vs. linux kernel build
  - From: Benjamin Herrenschmidt
- Re: Implicit altivec vs. linux kernel build
  - From: David Edelsohn

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