Hi Nick,
    
   First thanks for your reply.

>Is the "mipsx3" a MIPS processor variant ?  If so you might want to
>consider starting with the current mips target rather than the mmix.

Yes, MIPSX3 is a MIPS processor variant. But I find the gas MIPS is too 
complicated to integrate the MIPSX3 in it. Although the codes of 
tc-mipsx3.* is originated from tc-mips.*, I think treating MIPSX3 as a new 
processor maybe somewhat easier.

I have rename tc-mipsx3.c/tc-mipsx3.h to tc-mips.c/tc-mips.h in order to 
compile the porting codes. 

bash#./configure --target=mips-big-aout

I got a new "as" that can translate asm codes to binary codes. But it 
generates coff file, what I want is aout. This situation also confused me 
so much.

>Did you run "autoconf" (after changing configure.in) and then
>"automake" (after changing Makefile.am) in the gas source directory ?
>These tools create the "configure" and "Makefile.in" files
>respectively which are what are actually used when configuring gas.

surely. I had run "autoconf" and "automake" before doing "./configure"

Best regards
David.Z

_________________________________________________________________
ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger£º
http://messenger.microsoft.com/cn