On 12/24/15 07:07, Richard Henderson wrote:
> On 12/23/2015 01:48 PM, cheng...@emindsoft.com.cn wrote:
>> +static float32 sfmt_to_float32(uint64_t sfmt)
>> +{
>> + uint32_t sign = get_fsingle_sign(sfmt);
>> + uint32_t man = get_fsingle_man(sfmt);
>> + uint32_t exp = get_fsingle_exp(sfmt);
>> + float32 f;
>> +
>> + if (get_fsingle_calc(sfmt) == TILEGX_F_CALC_CVT) {
>> + if (sign) {
>> + f = int32_to_float32(0 - man, &fp_status);
>> + } else {
>> + f = uint32_to_float32(man, &fp_status);
>> + }
>> + exp += get_f32_exp(f) - 0x9e;
>> + if ((int32_t) exp < 0) {
>> + return float32_infinity | float32_set_sign(float32_zero, sign);
>> + } else if (exp >= 0xff) {
>> + return float32_zero | float32_set_sign(float32_zero, sign);
>> + } else {
>> + set_f32_exp(&f, exp);
>> + }
>
>
> What in the world are you attempting to do here?
> This is not normalization. This is not even remotely
> correct with respect to zero or infinity.
>
For fdouble, I use almost the same way, but can get the correct result (
pass gcc testsuite for fdouble, include inf and zero tests). But tests
will never enough, we can not say the fdouble implementation must be OK.
So please help check the fdouble implementation in details, again, when
you have time, it may still have issues.
> Moreover, I thought we agreed to do away with that CALC bit.
>
OK, I will try, next.
I will copy and reconstruct related code from qemu fpu implementation
instead of (u)int32/64_to_float32/64 functions (just like you said, I
guess).
Hope I can finish within 2015-12-31.
Thanks.
--
Chen Gang (陈刚)
Open, share, and attitude like air, water, and life which God blessed
