From: Richard Hirst <rhirst@linuxcare.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gcc type promotion bug?
Date: Tue, 16 Apr 2002 20:36:14 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905460@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905457@msgid-missing>
On Tue, Apr 16, 2002 at 10:31:02PM +0200, Andreas Schwab wrote:
> 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.
OK, thanks. I looked at (out of date) K&R, which told me all floating
point arithmetic in C was done in double precision, and I tried my
program on i386, where it appeared to worked fine.
Cheers,
Richard
next prev parent reply other threads:[~2002-04-16 20:36 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
2002-04-16 20:36 ` Richard Hirst [this message]
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-105590701905460@msgid-missing \
--to=rhirst@linuxcare.com \
--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