All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Weber <thomas.weber.linux@googlemail.com>
To: ratheesh k <ratheesh.ksz@gmail.com>
Cc: Thomas Weber <thomas.weber.linux@googlemail.com>,
	Uriel Corfa <uriel@corfa.fr>,
	linux-c-programming@vger.kernel.org
Subject: Re: float
Date: Tue, 11 Jan 2011 09:57:15 +0100	[thread overview]
Message-ID: <4D2C1B6B.8000504@gmail.com> (raw)
In-Reply-To: <AANLkTimqjBgQXRq0+sm1FXfU3QEaDeo+ZR88Wxs8U3r5@mail.gmail.com>

Am 11.01.2011 09:34, schrieb ratheesh k:
> On Tue, Jan 11, 2011 at 1:31 PM, Thomas Weber
> <thomas.weber.linux@googlemail.com> wrote:
>> Okay, now I got it.
>>
>> Look for IEEE754.
>>
>> 0.1 is in double precision 0.10000000149011612
>>
>> Thomas
>>
> 
> Is it possible to print the correct "printf" statement by typecasting
> some of operations or  data types. I tried with no success.
> 
> -Ratheesh

Try something with precision and typecast float to double

printf("f:%.10f is 1.0 \n",(double) f);


Thomas

> 
> 
>> Am 11.01.2011 08:55, schrieb Uriel Corfa:
>>> I'd say : rounding errors. Floating point goes in mysterious ways.
>>>
>>> On Tue, Jan 11, 2011 at 8:38 AM, ratheesh k <ratheesh.ksz@gmail.com> wrote:
>>>> I could not understand  why it getting printed like this. Could any
>>>> body tell me.
>>>>
>>>> #include <stdio.h>
>>>>
>>>> int main()
>>>> {
>>>>        float f=0.0f;
>>>>        int i;
>>>>
>>>>        for(i=0;i<10;i++)
>>>>                f = f + 0.1f;
>>>>
>>>>        if(f == 1.0f)
>>>>                printf("f is 1.0 \n");
>>>>        else
>>>>                printf("f is NOT 1.0\n");
>>>>
>>>>        return 0;
>>>> }
>>>
>>


  reply	other threads:[~2011-01-11  8:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11  7:38 float ratheesh k
2011-01-11  7:46 ` float Thomas Weber
2011-01-11  7:56   ` float Amit Virdi
2011-01-11  7:55 ` float Uriel Corfa
2011-01-11  8:01   ` float Thomas Weber
2011-01-11  8:34     ` float ratheesh k
2011-01-11  8:57       ` Thomas Weber [this message]
2011-01-11  8:38 ` float Andrej Gelenberg
  -- strict thread matches above, loose matches on Subject: below --
2010-01-08 16:30 float phoenixxz
2010-01-08  4:42 ` float Bryan Christ
2010-01-08 16:45   ` float Fawad Lateef
2010-01-08 16:40 ` float Nanakos Chrysostomos
2010-01-08 16:44 ` float Fawad Lateef
2010-01-08 16:47 ` float Nanakos Chrysostomos
2010-01-08 17:11   ` float Michal Nazarewicz
2010-01-08 17:19     ` float Nanakos Chrysostomos
2010-01-08 17:21     ` float Nanakos Chrysostomos
2010-01-08 17:43       ` float Michal Nazarewicz
2010-01-08 18:00 ` float andrej.gelenberg
2010-01-08 22:05 ` float Glynn Clements

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D2C1B6B.8000504@gmail.com \
    --to=thomas.weber.linux@googlemail.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=ratheesh.ksz@gmail.com \
    --cc=uriel@corfa.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.