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: [RFC] optabs and tree-codes for vector operations

From: Devang Patel <dpatel at apple dot com>
To: Richard Henderson <rth at redhat dot com>
Cc: James E Wilson <wilson at specifixinc dot com>, Dorit Naishlos <DORIT at il dot ibm dot com>, gcc at gcc dot gnu dot org
Date: Wed, 18 Aug 2004 13:35:44 -0700
Subject: Re: [RFC] optabs and tree-codes for vector operations
References: <OFF27DB315.64DA68A4-ONC2256EEB.00746817-C2256EEB.0075C359@il.ibm.com> <411C100D.7050502@specifixinc.com> <20040815065711.GA10717@redhat.com> <420EFB91-F14B-11D8-BD87-000393A91CAA@apple.com> <20040818195523.GA28818@redhat.com>

On Aug 18, 2004, at 12:55 PM, Richard Henderson wrote:

On Wed, Aug 18, 2004 at 12:17:34PM -0700, Devang Patel wrote:
So, we'd have one new optab to for VEC_COND_EXPR. And we use target
hooks to expand appropriately based on target requirements?
Hmm? Why do you need target hooks for this?

To allow targets to interpret vector compare results appropriately? I am on shaky ground here because I am still not completely able to understand how current rtl vector operations are working.

-
Devang

Follow-Ups:
- Re: [RFC] optabs and tree-codes for vector operations
  - From: Richard Henderson

References:
- [RFC] optabs and tree-codes for vector operations
  - From: Dorit Naishlos
- Re: [RFC] optabs and tree-codes for vector operations
  - From: James E Wilson
- Re: [RFC] optabs and tree-codes for vector operations
  - From: Richard Henderson
- Re: [RFC] optabs and tree-codes for vector operations
  - From: Devang Patel
- Re: [RFC] optabs and tree-codes for vector operations
  - From: Richard Henderson

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