This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Fwd: Re: [PATCH] MIPS32 DSP instructions again]


>>>>> "Richard" == Richard Sandiford <rsandifo@nildram.co.uk> writes:

 Richard> Eric Christopher <echristo@redhat.com> writes:
 >>> The MIPS DSP architecture manual uses the $ac syntax, it's also
 >>> been used by other toolchain companies who have updated their
 >>> assemblers to support the DSP ASE, and there's now quite a
 >>> significant amount of DSP assembler code written by various
 >>> parties which will be using $ac. I'd prefer it if we could stick
 >>> with $ac but, if you insist, then would supporting both $ac and
 >>> $acc as aliases be acceptable?
 >> [...]  Yes, you can have $ac as an alias.

 Richard> You mean we should still acccept $accX as well?  If so, I
 Richard> think that's just going to lead to confusion....

 Richard> If the official docs, other tools, and recommended usage all
 Richard> say "$acX", is there really any benefit in accepting "$accX"
 Richard> as well?  Sure, some other architectures use "accX"-like
 Richard> names, but other architectures also give their integer
 Richard> registers names like "$rX" or plain "rX".  I don't see that
 Richard> as any reason for MIPS assemblers to accept those names too.

Agreed.  If the MIPS specs call it ACn, let that be the name used in
GAS.  The naming used in other processor types is really not relevant
at all.

   paul


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]