This is the mail archive of the gcc-patches@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: [i386] pni => sse3 -- GCC 3.3.3 related

From: Jim Wilson <wilson at specifixinc dot com>
To: "H. J. Lu" <hjl at lucon dot org>
Cc: Kelley Cook <kelleycook at yahoo dot com>, gcc-patches at gcc dot gnu dot org, GCC MailingList <gcc at gcc dot gnu dot org>
Date: Fri, 20 Feb 2004 17:11:03 -0800
Subject: Re: [i386] pni => sse3 -- GCC 3.3.3 related
References: <402015DF.8030507@ford.com> <402017A8.6040009@ford.com> <m3znbylwix.fsf@uniton.integrable-solutions.net> <20040205011120.GA25895@lucon.org> <m3oesenwxk.fsf@uniton.integrable-solutions.net> <20040206174131.GA388@lucon.org>

H. J. Lu wrote:

2004-02-06  H.J. Lu  <hongjiu.lu@intel.com>
	* doc/invoke.texi: Mention SSE2 and SSE3.
	* config/i386/i386.h: Deprecate -mpni/-mno-pni.
2004-02-03  Kelley Cook  <kcook@gcc.gnu.org>
	* config/i386/i386.c: Rename pni to sse3.

> ...

OK for mainline and 3.4. 3.3 would be Gaby's call.

I see that you still define __PNI__. Do we really need that? Maybe there should be some planned obsolescence for that? I.e., we continue to support it for now in 3.3 but not in 3.4, or we support it in 3.4 but not in 3.5? -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

References:
- [i386] pni => sse3 -- GCC 3.3.3 related
  - From: Kelley Cook
- Re: [i386] pni => sse3 -- GCC 3.3.3 related
  - From: Kelley Cook
- Re: [i386] pni => sse3 -- GCC 3.3.3 related
  - From: Gabriel Dos Reis
- Re: [i386] pni => sse3 -- GCC 3.3.3 related
  - From: H. J. Lu
- Re: [i386] pni => sse3 -- GCC 3.3.3 related
  - From: Gabriel Dos Reis
- Re: [i386] pni => sse3 -- GCC 3.3.3 related
  - From: H. J. Lu

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