Re: btrfs zero divide

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Geert Uytterhoeven dixit:

>   0:	222e ff74      	movel %fp@(-140),%d1
>   4:	2a2e ff5c      	movel %fp@(-164),%d5
>   8:	2c2e ff60      	movel %fp@(-160),%d6
>   c:	4c45 1402     <	divul %d5,%d2,%d1 >
>  10:	2d40 ff64      	movel %d0,%fp@(-156)
>  14:	2d41 ff68      	movel %d1,%fp@(-152)
>  18:	2205           	movel %d5,%d1
>  1a:	4c2e 1800 ff68 	mulsl %fp@(-152),%d1
>  20:	4c04 0800      	mulsl %d4,%d0
>  24:	2041           	moveal %d1,%a0
>  26:	d1c0           	addal %d0,%a0
>  28:	2206           	movel %d6,%d1
>  2a:	4c2e 1400 ff68 	mulul %fp@(-152),%d0,%d1

This is gcc-4.8 compiled, btw… in case that’s a known issue.

bye,
//mirabilos
-- 
“It is inappropriate to require that a time represented as
 seconds since the Epoch precisely represent the number of
 seconds between the referenced time and the Epoch.”
	-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux