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: [Fwd: Re: [PATCH] MIPS32 DSP instructions again]


Re: [Fwd: Re: [PATCH] MIPS32 DSP instructions again]Hello,

  Based on your review, I made some changes to the DSP
patch as follows.

1. Fix space in tc-mips.c.
2. Change code to check signed immediate using min_range and
max_range.
3. Create a new attribute for 10-bit signed immediate.
4. Add comments in mips-opc.c to explain attributes added to
   DSP instructions.

  GAS "make check" is ok.  According to my manager, our DSP ASE
document will be released in 3 weeks.  Then, you can review the
table for DSP instructions.  Thanks a lot!

Regards,
Chao-ying

[My last email didn't go to binutils, so I sent it again.]

----- Original Message ----- 
From: Eric Christopher
To: Fu, Chao-Ying
Cc: Thiemo Seufer ; dom@mips.com ; ian@airs.com ; Paul Koning ;
nigel@mips.com ; Richard Sandiford ; radhika@mips.com ;
binutils@sourceware.org
Sent: Monday, June 13, 2005 3:52 PM
Subject: Re: [Fwd: Re: [PATCH] MIPS32 DSP instructions again]


On Mon, 2005-06-13 at 15:47 -0700, Chao-ying Fu wrote:
> Hi Eric,
>
>   Do you think it's better to check in DSP stuff after
> the DSP ASE document is released?  I think the code
> will be more clear with the document.  Maybe I
> will just hold the patch for a while.  Thanks!
OK. If you get the rest of the cosmetic changes done (magic numbers,
ranges, spacing, etc) I'll review that part and we can get it to where
once the doc comes out it shouldn't be much work (if any) to get the
full patch accepted.
How's that?
-eric

Attachment: mips32-dsp.s
Description: Binary data

Attachment: mips32-dsp.d
Description: Binary data

Attachment: mips32-dsp.l
Description: Binary data

Attachment: dsp06212005.diff
Description: Binary data


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