Mips16 question...

[mike stump]

> From: Shane Nay <shane@minirl.com>
> To: gcc@gcc.gnu.org
> 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.

Shouldn't be too hard to put a ! TARGET_MIPS16 on the instructions...

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.