This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: [PATCH] MIPS32 DSP instructions again
- From: Eric Christopher <echristo at redhat dot com>
- To: Chao-ying Fu <fu at mips dot com>
- Cc: Nigel Stephens <nigel at mips dot com>, Richard Sandiford <rsandifo at redhat dot com>, "Thekkath, Radhika" <radhika at mips dot com>, binutils at sourceware dot org
- Date: Tue, 07 Jun 2005 20:04:04 -0700
- Subject: Re: [PATCH] MIPS32 DSP instructions again
- References: <B5B9CAE3-D2C9-11D9-BE69-003065BDF310@apple.com> <1117671176.4744.67.camel@localhost.localdomain> <87r7flusey.fsf@firetop.home> <1117735089.22225.3.camel@localhost.localdomain> <42A5B577.6080603@mips.com> <1118165083.5438.5.camel@localhost.localdomain> <000801c56bb9$bd9ea620$a914a8c0@MIPS.COM> <1118188909.5438.74.camel@localhost.localdomain> <000b01c56bc3$d2a06950$a914a8c0@MIPS.COM>
> 10 new operand formats, 3, 4, 5, 6, 7, 8, 9, 0, ', :. These
> new DSP instructions are considered as part of the MIPS32
> instructions, so there is no gas flag to enable or disable them.
I've not looked at the rest, but I'm not sure that this part is
acceptable. What you're saying is that these aren't part of any
particular ASE, but also weren't part of the core description that was
published back in 99 or so? I don't think that we should allow
instructions to be assembled for any core that doesn't support them.
Since, IIRC, there are extant MIPS32 parts out in the world that means
we'll need a switch for this.
Your thoughts?
-eric