HBO043%DJUKFA11.BITNET@cunyvm.cuny.edu (Christoph van Wuellen) (06/08/90)
I change my policy and ship out a patch upon every bug I fix.
This is what I noticed when trying to compile and run tar(1):
If integer constants which appear with different sizes (e.g. short and long)
are mapped to CPU registers, they do not automatically have the maximum
size. In function copy(), file tar.c, 512 is mapped to d6,
initialized as d6.w and used as d6.l { (long) BLOCK_SIZE }.
It is a trivial fix to keep such an expression in the expression-lookup
table with its maximum size.
C.v.W
begin 644 patch_04.Z
M'YV-(Q)009-F#HB"(,* F(.F#!LV">6,(6BGC L% :64:?.F(H@R%>7DH4/0z
MS9F$8CJ62>B&S$$W8]C4(9/&) B2*\?4H0."34V+& 4V= -"3AVB.(N6F</Sy
MC9F;#4&82<-F)4DY;^J<0;,0S<41+<*VT,FSH9PR8L.2!6$6;=JU;=..W<FVx
MS-FT(S"&>"&FY@N&&+N&D:,#A.$I#1^"""*1HMV@4HY"76GFS<,W=VJ>I%,&w
M#\_,)$'P]<OPYAL08\Z&X:PC:!@W8=CDT6-QC(LQ-,T$'HAP\,0T'E.765V&v
M3&$C<M* 4"(9! X0,6[H@!%#1PP;T'/D@*%@S&H0/'B X#(%21 I7XH\,0+"u
M!\O8LVO?SJU A?WWLFG?3M#D#5'F1(% P@R5!>=#C4\%X-VW(D%@@LNO#"&t
M#3B\\!I\^HV1 '+* 6B8@C;H,$,..M!00W;;U6??BBRVJ*(*T"W(0@PR#,BBs
M @[&(&,,,\0 0EH*&); &'/ T8(/=KR1!AE/]0 "##L$"4("EA7$DY-$PA&Er
MD&?148<<1&49Y0J&E=G'1VS,L=(>"I"9P LJM#DE"# FX09G9]B%FG],O4:'q
M06V$D0<(8JQ4TV0WA2%&52" QE5N9MA5QIUR)D#G0FG09E!8(*Q11AEP(!HHp
M'FFT44<;F-(&0J5TOE!I&D^AX,8;9*#EPZRUTI$''"OUX.2D7Z0QAG\@F& "o
M"+C:NE2F*[F7Y9&=&>G#LK2EP&J9STZ+A[34]HHLK<K.P>R691K6AY3EKK "n
K"MG6H>8<*9!;+JP@H$"&NV586]YYZ:T75!$M@>!45PY!Y)MC"G26!D_< ; "m
l
end