Re: [PATCH] simulator for mips3264

[Andrew Cagney <ac131313 at cygnus dot com>]

> And now the tables are turned!  Muhahahahaha!  8-)
> 
> 
>> So, the issues / questions:
>> 
>> (1) "using how?" / "tested how?"
>> 
> 
> 
> I deserved that one.  I really did  [;)] 
> 
> mipsisa32-elf gcc. Internal port for another chip. Using it as a
> simulator for execution testing for gcc.
> 
> 
>> (2) why bother define the do_foo functions in m3264.igen, when they're
>> only used in one function?
>> 
> 
> 
> Infrastructure.  May need them again some day.

That and the reality that it is easier to debug / breakpoint those 
functions than the semantic code.

Recent fixes should have greatly improved this.  GDB can (when someone 
doesn't break GCC ...) correctly step through complex #line sequences.

>> (3) why did you add clo/clz in mips.igen?  I know there are some
>> non-true-mips32/mips64 CPUs which implement them...  but they also
>> implement madd/maddu/msub/msubu.  Any argument that puts these in
>> mips.igen also puts the rest, as far as I can see.
>> 
> 
> 
> Ok. I can do this...
> 
> 
>> Personally, if I were doing this ("oh wait, we did, but I've not
>> had time to go back and submit it all yet!" 8-) I'd put the new
>> mips32/mips64 instructions into mips.igen, since they're neither
>> particular chip-specific and they're not an ASE either.
>> 
> 
> 
> Or this.  Pick one  [:)] 

Yes, true.

	mips.igen	official ISAs
	tx.igen		tosh ISAs
	vr.igen		NEC ISAs

Mind you mips.igen is getting a little large.

	Andrew