This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils 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] Add a second 'pinfo' member to mips_opcode to extendnumber of available bits

From: Eric Christopher <echristo at redhat dot com>
To: fnf at specifixinc dot com
Cc: Richard Sandiford <rsandifo at redhat dot com>, binutils at sources dot redhat dot com
Date: Fri, 21 Jan 2005 10:38:33 -0800
Subject: Re: [PATCH] Add a second 'pinfo' member to mips_opcode to extendnumber of available bits
References: <200501191519.59986.fnf@specifixinc.com> <wvnmzv471xr.fsf@talisman.cambridge.redhat.com> <1106243981.4970.0.camel@localhost.localdomain> <200501211235.14273.fnf@specifixinc.com>

On Fri, 2005-01-21 at 12:35 -0600, Fred Fish wrote:
> On Thursday 20 January 2005 11:59, Eric Christopher wrote:
> > On Thu, 2005-01-20 at 11:52 +0000, Richard Sandiford wrote:
> > > Just a suggestion (I've no authority here ;) but maybe it would
> > > be better to use names like INSN2_* for flags that apply to pinfo2?
> > > Less chance of using the wrong pinfo field accidentally.
> > 
> > Seems like a good idea to me.
> 
> OK, here is a patch to do that.  I'll apply it if it looks OK.

Looks mostly mechanical. Go ahead. :)

-eric

References:
- [PATCH] Add a second 'pinfo' member to mips_opcode to extend number of available bits
  - From: Fred Fish
- Re: [PATCH] Add a second 'pinfo' member to mips_opcode to extendnumber of available bits
  - From: Richard Sandiford
- Re: [PATCH] Add a second 'pinfo' member to mips_opcode to extendnumber of available bits
  - From: Eric Christopher
- Re: [PATCH] Add a second 'pinfo' member to mips_opcode to extend number of available bits
  - From: Fred Fish

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