Fix to fix

This commit is contained in:
ceriel 1991-03-25 13:16:02 +00:00
parent 043ad764b8
commit 8b67c1f800
8 changed files with 28 additions and 24 deletions

View file

@ -1,10 +1,11 @@
The file 'table' in this directory contains a back end table for the
MC68020 processor as well as one for the MC68000. Both tables use 4 bytes
for words as well as for pointers. The table must be preprocessed first
MC68020 processor as well as one for the MC68000. Both tables use 2 or 4 bytes
for words and 4 bytes for pointers. The table must be preprocessed first
by the C preprocessor.
The file "whichone.h" specifies which code generator is generated:
it #defines either TBL68000 or TBL86020.
it #defines either TBL68000 or TBL86020, and it defines WORD_SIZE to either
2 or 4.
The m68k4(TBL68000) cg can very well be used for the MC68010 processor,
for it makes rather efficient use of the 68010 loop mode.
The mach.[ch] files are also suitable for both the m68020 and the m68k4.
The mach.[ch] files are also suitable for both the m68020 and the m68k[24].

View file

@ -4765,7 +4765,7 @@ proc logndef
with any_int STACK
uses AA_REG,
DD_REG,
DD_REG4
DD_REG4={const,0}
gen
move %1, %c.1
lea {regAregXcon, sp, %c, 1, 0},%a
@ -4869,7 +4869,7 @@ with DD_REG STACK
pat com !defined($1)
with any_int STACK
uses AA_REG,
DD_REG4
DD_REG4={const,0}
gen move %1, %b.1
move_l sp, %a
asr_l {small_const, 1}, %b

View file

@ -1,10 +1,11 @@
The file 'table' in this directory contains a back end table for the
MC68020 processor as well as one for the MC68000. Both tables use 4 bytes
for words as well as for pointers. The table must be preprocessed first
MC68020 processor as well as one for the MC68000. Both tables use 2 or 4 bytes
for words and 4 bytes for pointers. The table must be preprocessed first
by the C preprocessor.
The file "whichone.h" specifies which code generator is generated:
it #defines either TBL68000 or TBL86020.
it #defines either TBL68000 or TBL86020, and it defines WORD_SIZE to either
2 or 4.
The m68k4(TBL68000) cg can very well be used for the MC68010 processor,
for it makes rather efficient use of the 68010 loop mode.
The mach.[ch] files are also suitable for both the m68020 and the m68k4.
The mach.[ch] files are also suitable for both the m68020 and the m68k[24].

View file

@ -4765,7 +4765,7 @@ proc logndef
with any_int STACK
uses AA_REG,
DD_REG,
DD_REG4
DD_REG4={const,0}
gen
move %1, %c.1
lea {regAregXcon, sp, %c, 1, 0},%a
@ -4869,7 +4869,7 @@ with DD_REG STACK
pat com !defined($1)
with any_int STACK
uses AA_REG,
DD_REG4
DD_REG4={const,0}
gen move %1, %b.1
move_l sp, %a
asr_l {small_const, 1}, %b

View file

@ -1,10 +1,11 @@
The file 'table' in this directory contains a back end table for the
MC68020 processor as well as one for the MC68000. Both tables use 4 bytes
for words as well as for pointers. The table must be preprocessed first
MC68020 processor as well as one for the MC68000. Both tables use 2 or 4 bytes
for words and 4 bytes for pointers. The table must be preprocessed first
by the C preprocessor.
The file "whichone.h" specifies which code generator is generated:
it #defines either TBL68000 or TBL86020.
it #defines either TBL68000 or TBL86020, and it defines WORD_SIZE to either
2 or 4.
The m68k4(TBL68000) cg can very well be used for the MC68010 processor,
for it makes rather efficient use of the 68010 loop mode.
The mach.[ch] files are also suitable for both the m68020 and the m68k4.
The mach.[ch] files are also suitable for both the m68020 and the m68k[24].

View file

@ -4765,7 +4765,7 @@ proc logndef
with any_int STACK
uses AA_REG,
DD_REG,
DD_REG4
DD_REG4={const,0}
gen
move %1, %c.1
lea {regAregXcon, sp, %c, 1, 0},%a
@ -4869,7 +4869,7 @@ with DD_REG STACK
pat com !defined($1)
with any_int STACK
uses AA_REG,
DD_REG4
DD_REG4={const,0}
gen move %1, %b.1
move_l sp, %a
asr_l {small_const, 1}, %b

View file

@ -1,10 +1,11 @@
The file 'table' in this directory contains a back end table for the
MC68020 processor as well as one for the MC68000. Both tables use 4 bytes
for words as well as for pointers. The table must be preprocessed first
MC68020 processor as well as one for the MC68000. Both tables use 2 or 4 bytes
for words and 4 bytes for pointers. The table must be preprocessed first
by the C preprocessor.
The file "whichone.h" specifies which code generator is generated:
it #defines either TBL68000 or TBL86020.
it #defines either TBL68000 or TBL86020, and it defines WORD_SIZE to either
2 or 4.
The m68k4(TBL68000) cg can very well be used for the MC68010 processor,
for it makes rather efficient use of the 68010 loop mode.
The mach.[ch] files are also suitable for both the m68020 and the m68k4.
The mach.[ch] files are also suitable for both the m68020 and the m68k[24].

View file

@ -4765,7 +4765,7 @@ proc logndef
with any_int STACK
uses AA_REG,
DD_REG,
DD_REG4
DD_REG4={const,0}
gen
move %1, %c.1
lea {regAregXcon, sp, %c, 1, 0},%a
@ -4869,7 +4869,7 @@ with DD_REG STACK
pat com !defined($1)
with any_int STACK
uses AA_REG,
DD_REG4
DD_REG4={const,0}
gen move %1, %b.1
move_l sp, %a
asr_l {small_const, 1}, %b