From: Leon Romanovsky <leonro@mellanox.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Bart Van Assche <bvanassche@acm.org>,
Jason Gunthorpe <jgg@mellanox.com>,
Kees Cook <keescook@chromium.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH] Avoid that check_shl_overflow() triggers a compiler warning when building with W=1
Date: Fri, 8 Mar 2019 15:53:22 +0000 [thread overview]
Message-ID: <20190308155318.GG32625@mtr-leonro.mtl.com> (raw)
In-Reply-To: <ca0d8714-3258-3155-247c-af2d63c28273@rasmusvillemoes.dk>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
On Fri, Mar 08, 2019 at 09:09:46AM +0100, Rasmus Villemoes wrote:
> On 08/03/2019 08.01, Leon Romanovsky wrote:
> >
> > Mathematical therm for discrete numbers greater or equal to zero is
> > "normal numbers".
>
> Sorry, WHAT? "Normal" is used and abused for a lot of things in
> mathematics, but I have never heard it used that way. When attached to
> the word "number", it means a real number with certain properties
> related to its digit expansion(s). And then of course there's the
> isnormal() thing for floating point values in C/computing.
It is hard to argue with this type of arguments: "never heard -> doesn't
exist". Luckily enough for me who can't find my fifth grade textbook
from school, we have Wikipedia which has pointer to ISO standard with
clear declaration of "normal numbers" as 0,1,2, ....
https://en.wikipedia.org/wiki/Natural_number#cite_note-ISO80000-1
"Standard number sets and intervals". ISO 80000-2:2009. International
Organization for Standardization. p. 6.
>
> Strong NAK to using is_normal/is_negative.
>
> Rasmus
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2019-03-08 15:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 1:01 [PATCH] Avoid that check_shl_overflow() triggers a compiler warning when building with W=1 Bart Van Assche
2019-03-07 1:24 ` Jason Gunthorpe
2019-03-07 2:14 ` Bart Van Assche
2019-03-07 7:18 ` Rasmus Villemoes
2019-03-08 0:08 ` Bart Van Assche
2019-03-08 7:01 ` Leon Romanovsky
2019-03-08 8:09 ` Rasmus Villemoes
2019-03-08 15:53 ` Leon Romanovsky [this message]
2019-03-08 21:32 ` Rasmus Villemoes
2019-03-08 7:58 ` Rasmus Villemoes
2019-03-08 12:41 ` Jason Gunthorpe
2019-03-07 7:24 ` Leon Romanovsky
2019-03-07 14:53 ` Bart Van Assche
2019-03-07 15:40 ` Leon Romanovsky
2019-03-07 16:52 ` Kees Cook
2019-03-07 17:02 ` Leon Romanovsky
2019-03-07 17:12 ` Kees Cook
2019-03-07 17:36 ` Leon Romanovsky
2019-03-07 20:28 ` Rasmus Villemoes
2019-03-08 7:03 ` Leon Romanovsky
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=20190308155318.GG32625@mtr-leonro.mtl.com \
--to=leonro@mellanox.com \
--cc=bvanassche@acm.org \
--cc=jgg@mellanox.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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