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: fix 20650

From: Geoff Keating <geoffk at apple dot com>
To: Segher Boessenkool <segher at kernel dot crashing dot org>
Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Richard Henderson <rth at redhat dot com>, David Edelsohn <dje at watson dot ibm dot com>
Date: Thu, 7 Apr 2005 17:00:05 -0700
Subject: Re: fix 20650
References: <20050402095730.F15491D4534@geoffk5.apple.com> <200504021904.j32J4vD27790@makai.watson.ibm.com> <ff7eb37444655d267dff52f70ebffd59@apple.com> <8c28c497145378d0071765ee5641899f@kernel.crashing.org>

On 06/04/2005, at 4:53 AM, Segher Boessenkool wrote:

There must be other ports that have instructions that can operate only on memory; does anyone know an example?

i386 fnstsw (i.e., *cmpfp_<mode>).

I don't see how memory is involved in those at all; everything is register_operand.

Also RS6000 already has some: lfq, stfq, lmw, stmw.

I meant, an instruction that's generated from optabs. For instance, a port where the 'add' operation can only take memory operands.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

References:
- fix 20650
  - From: Geoffrey Keating
- Re: fix 20650
  - From: David Edelsohn
- Re: fix 20650
  - From: Geoffrey Keating
- Re: fix 20650
  - From: Segher Boessenkool

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