This is the mail archive of the
mailing list for the GCC project.
Re: Mips16 question...
- To: mike stump <mrs at windriver dot com>, gcc at gcc dot gnu dot org, shane at minirl dot com
- Subject: Re: Mips16 question...
- From: Shane Nay <shane at minirl dot com>
- Date: Wed, 29 Aug 2001 14:26:35 -0700
- References: <200108292050.NAA27029@kankakee.wrs.com>
On Wednesday 29 August 2001 13:50, mike stump wrote:
> > From: Shane Nay <firstname.lastname@example.org>
> > To: email@example.com
> > Date: Wed, 29 Aug 2001 11:32:26 -0700
> > However with the 3.0 release, it seems to be shooting off all
> > sorts of strange pieces of assembly, opcodes that are only in
> > mips I/II/III, distinctly not in mips16.
> If you have the testing time... Try a current cvs pull from the
> top of the tree, and submit bug reports for the stuff that fails.
Yea, I pulled that down, now I'm getting some strangeness from
binutils. It's complaining about perfectly valid instructions...,
Ugh. (2.11.2 & CVS)
> Shouldn't be too hard to put a ! TARGET_MIPS16 on the
Explain ..., how does this work?
> A snippet of the assembly code that is wrong would make fixing it a
> bit easier. If someone has a pointer to the mips16 documentation,
> it needs to be added to the readings list.
Sure, clearly. I'll try to get some broken test cases with present
CVS. As far as MIPS16 documentation, the best I know is the VR4181
documentation includes a pretty good instruction by instruction
(I'd give you a direct link, but their site doesn't work well with
that, it's under Microprocessors and the data sheet for the VR4181)