From: Vincent Lefevre <vincent+gcc@vinc17.org>
To: Liu Hao <lh_mouse@126.com>, Andrew Haley <aph@redhat.com>,
Neha Gowda <neha.gnu.gcc@gmail.com>,
gcc-help@gcc.gnu.org
Subject: Re: Should rand() return a RAND_MAX value for 32 bit target?
Date: Thu, 20 Sep 2018 16:12:00 -0000 [thread overview]
Message-ID: <20180920161204.GB304@joooj.vinc17.net> (raw)
In-Reply-To: <20180920155829.GA304@joooj.vinc17.net>
On 2018-09-20 17:58:30 +0200, Vincent Lefevre wrote:
> On 2018-09-20 23:21:23 +0800, Liu Hao wrote:
> > `2147483647` is an integer constant. This rule only describes floating
> > constants, so it does not apply.
>
> Actually the fact that it is a constant doesn't matter, but...
>
> > According to '6.3.1.8 Usual arithmetic conversions', here `2147483647`
> > is converted to a value having type `float`, which is then compared with
> > `f` using the internal `long double` type.
>
> The conversion of the int needs to be done with the precision and
> range of long double since this is neither an assignment nor a cast.
Similarly, for
float a, b;
double c;
(a + b) + c;
I would expect the result of a + b to be kept in long double instead
of being converted to double due to the operand c.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2018-09-20 16:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 12:22 Neha Gowda
2018-09-18 13:09 ` Xi Ruoyao
2018-09-18 13:17 ` Xi Ruoyao
2018-09-18 13:49 ` Jonathan Wakely
2018-09-18 13:46 ` Andrew Haley
2018-09-20 14:42 ` Vincent Lefevre
2018-09-20 15:05 ` Vincent Lefevre
2018-09-20 15:21 ` Liu Hao
2018-09-20 15:58 ` Vincent Lefevre
2018-09-20 16:12 ` Vincent Lefevre [this message]
2018-09-21 2:49 ` Liu Hao
2018-09-22 8:17 ` Vincent Lefevre
2018-09-22 10:08 ` Vincent Lefevre
2018-09-22 13:52 ` Liu Hao
2018-09-22 22:12 ` Vincent Lefevre
2018-09-20 15:46 ` Dennis Clarke
2018-09-20 16:16 ` Vincent Lefevre
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=20180920161204.GB304@joooj.vinc17.net \
--to=vincent+gcc@vinc17.org \
--cc=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lh_mouse@126.com \
--cc=neha.gnu.gcc@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).