public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gcc type promotion bug?
Date: Tue, 16 Apr 2002 20:31:02 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905459@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905457@msgid-missing>

Richard Hirst <rhirst@linuxcare.com> writes:

|> #include <stdio.h>
|> 
|> int
|> main(int argc, char **argv)
|> {
|>         long a = 0x70000037L;
|>         float f = 0.01;
|>         long b = a + 1L/f;
|> 
|>         printf("%lx, %lx\n", b, a + 100L);
|>         return 0;
|> }
|> 
|> 
|> 
|> In the above, 1/f = 100, so the two numbers printed out should be the
|> same.  For me it prints out "70000080, 7000009b".  Same for gcc 2.96
|> and 3.0.3.
|> 
|> By trying various numbers for 'a', it appears to me that it is demoting
|> 'a' to a float when evaluating 'b', thus truncating it to 24 significant
|> bits.  I thought all mixed mode arithmetic was supposed to be promoted
|> to doubles for evaluation.

No.  There are no operands of type double or long double involved, so the
ususal arithmetic conversions (6.3.1.8) choose float as the common type:

    Otherwise, if the corresponding real type of either operand is float,
    the other operand is converted, without change of type domain, to a
    type whose corresponding real type is float.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2002-04-16 20:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 20:00 [Linux-ia64] gcc type promotion bug? Richard Hirst
2002-04-16 20:31 ` Andreas Schwab [this message]
2002-04-16 20:36 ` Richard Hirst
2002-04-16 20:58 ` Andreas Schwab

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=marc-linux-ia64-105590701905459@msgid-missing \
    --to=schwab@suse.de \
    --cc=linux-ia64@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox