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: [patch 2/2] AMD bdver2 processors - TBM

From: Richard Henderson <rth at redhat dot com>
To: Quentin Neill <quentin dot neill dot gnu at gmail dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Thu, 04 Nov 2010 10:36:33 -0700
Subject: Re: [patch 2/2] AMD bdver2 processors - TBM
References: <AANLkTimu68wDKTwxP2bfvHdr+VK_rndkQuHjX4xHL1vJ@mail.gmail.com> <AANLkTi=MZRqhi1=jQ03C8-=djK4tdW=sQJ5FgKExj06Y@mail.gmail.com> <4CCCBE41.7080009@redhat.com> <AANLkTinmzgspzmeeYQf8M9QHMNpbkBnPqKZ2ENi4x3eg@mail.gmail.com> <4CD2DD2D.3060208@redhat.com> <AANLkTikw09MNPQ9no-r+rHwacye+_8duyCtmRGMYx=CU@mail.gmail.com>

On 11/04/2010 09:43 AM, Quentin Neill wrote:
>> Watch the extra vertical whitespace.
> 
> So should I have two lines (to separate list of ';TBM instructions')
> or just one?

Just one.

> So pulling the two bytes out in the builtin expander - should that be
> done with a *new* define_expand?  Or is there a set of RTX operations
> (shift, mask) I should use in the define_insn as written?

There's a set of C operators you may use.  ;-)

This is an *immediate*.  It's value is INTVAL (op1).
You can pull bits out from that and use GEN_INT to
pass the new rtl on to the define_insn.

r~

References:
- Re: [patch 2/2] AMD bdver2 processors - TBM
  - From: Quentin Neill
- Re: [patch 2/2] AMD bdver2 processors - TBM
  - From: Richard Henderson
- Re: [patch 2/2] AMD bdver2 processors - TBM
  - From: Quentin Neill

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