darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Correct fr30 comment

Browse source 
* fr30.cpu (f.m4): Replace bogus comment with a better guess
	at what is really going on.
This commit is contained in:
Alan Modra 2016-03-03 12:19:36 +10:30
parent b3258e643d
commit 439baf7121
2 changed files with 10 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
cpu/ChangeLog
View file

@ -1,3 +1,8 @@
2016-03-03 Alan Modra <amodra@gmail.com>
* fr30.cpu (f-m4): Replace bogus comment with a better guess
at what is really going on.
2016-03-02 Alan Modra <amodra@gmail.com> 2016-03-02 Alan Modra <amodra@gmail.com>
* fr30.cpu (f-m4): Replace -1 << 4 with -16. * fr30.cpu (f-m4): Replace -1 << 4 with -16.

8
cpu/fr30.cpu
View file

@ -159,10 +159,12 @@
(dnf f-u4c "4 bit 0 extended" () 12 4) (dnf f-u4c "4 bit 0 extended" () 12 4)
(df f-i4 "4 bit sign extended" () 8 4 INT #f #f) (df f-i4 "4 bit sign extended" () 8 4 INT #f #f)
(df f-m4 "4 bit minus extended" () 8 4 UINT (df f-m4 "4 bit minus extended" () 8 4 UINT
; ??? This field takes a value in the range [-16,-1] but there
; doesn't seem a way to tell CGEN that. Use an unsigned field and
; disable range checks on insertion by masking. Restore the sign
; on extraction. CGEN generated documentation for insns that use
; this field will be wrong.
((value pc) (and WI value (const #xf))) ((value pc) (and WI value (const #xf)))
; ??? On a 64 bit host this doesn't get completely sign extended
; if the value is recorded in a long, as it is during extraction.
; Various fixes exist, pick one.
((value pc) (or WI value (const -16))) ((value pc) (or WI value (const -16)))
) )
(dnf f-u8 "8 bit unsigned" () 8 8) (dnf f-u8 "8 bit unsigned" () 8 8)