On Fri, 23 Mar 2007 11:21:57 +0000
Gavin Maltby <[EMAIL PROTECTED]> wrote:

> Hi,
> 
> On 03/23/07 02:00, [EMAIL PROTECTED] wrote:
> > Hi, in the UltraSPARC III user's manual, section 7.11 on page 175 describes
> > instruction formats. On page 176 the last two instructions are exactly the
> > same, i.e.
> > 
> >  ----------------------------------------
> > |op|  fcn  |   op3   |        ---        |
> >  ----------------------------------------
> > 
> >  ----------------------------------------
> > |op|  fcn  |   op3   |        ---        |
> >  ----------------------------------------
> > 
> > Is this a mistake or there is a reason for two identical diagrams for the
> > same instruction format??
> 
> Can you give a documentation part number and revision.  In the documentation
> I'm looking at the only encodings that match the above are:
> 
> ----------------------------------------
> |op   |  fcn  |   op3   |        ---   |
> ----------------------------------------
>   31 30 29   25 24     19 18            0
> ----------------------------------------
> |op   |  rd   |   op3   |        ---   |
> ----------------------------------------
> 
> ie in the second there is an 'rd'.
> 
> I'm referring to some internal documentation for the particular
> sparc v9 implementations of UltraSPARC-III and other processors;
> it's based on the SPARC Arch Manual v9, and typically includes
> all the fixed errata from that (You can download the errata from
> sparc.org I think).
> 
> Gavin

http://www.sun.com/processors/manuals/USIIIv2.pdf

Go to section 7.11 page 176, in figure 7-2 the last two instruction formats are
exactly the same. I'd like to know if they have been duplicated by a mistake or
if there is a specific reason for duplicate instruction formats, or maybe the
last instruction is supposed to be |op|rd|op3|---| but instead of rd field it
has fcn??
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to