From: Alexander Cherepanov <ch3root@openwall.com>
To: musl@lists.openwall.com
Subject: Re: [musl] Minor style patch to exit.c
Date: Mon, 20 Jan 2020 00:02:04 +0300 [thread overview]
Message-ID: <d8bd0b30-d732-5926-9c37-3674ab241218@openwall.com> (raw)
In-Reply-To: <20200119162233.GD30412@brightrain.aerifal.cx>
On 19/01/2020 19.22, Rich Felker wrote:
>> Even if we know that _start + k == _end it doesn't mean that we
>> allowed to subtract them.
>
> Consider a function that takes a pointer p, an array a, and a length
> l, and does:
>
> for (i=0; i<l; i++) if (a+i == p) return p-a;
>
> Can f(_end,_start,k) and f(_start+k,_start,k) legitimately differ,
> despite _end==_start+k?
I guess it depends on what you mean by "legitimately" and "differ".
Given that _start and _end are different arrays the first variant is
undefined.
Counter-intuitive behavior of equal pointers could be demonstrated much
easier. Suppose x and y are two objects of the same type and &x + 1 ==
&y. Is it valid to evaluate the following expressions: *(&x + 1), &x +
2, (&y)[-1]?
> I think the answer is no, in the existing C
> language, in that the result of an expression is a pure function of
> the *values* put into it.
The fact that two values are equal doesn't mean that they are the same
value.
Take floating-point zeroes for example. They are equal but have
different provenances: one came from the right, another one -- from the
left:-)
> But compiler folks do not want to interpret
> it this way and are pushing through hidden "provenance" state, so...
IIUC they are not happy about it too but the alternatives are not that
great.
--
Alexander Cherepanov
next prev parent reply other threads:[~2020-01-19 21:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 11:07 Markus Wichmann
2020-01-19 11:12 ` Markus Wichmann
2020-01-19 11:31 ` Szabolcs Nagy
2020-01-19 12:17 ` Markus Wichmann
2020-01-19 13:33 ` Alexander Cherepanov
2020-01-19 14:24 ` Markus Wichmann
2020-01-19 14:49 ` Pascal Cuoq
2020-01-19 15:53 ` Alexander Cherepanov
2020-01-19 16:22 ` Rich Felker
2020-01-19 21:02 ` Alexander Cherepanov [this message]
2020-01-19 14:46 ` Alexander Monakov
2020-01-19 16:18 ` Rich Felker
2020-01-19 17:11 ` Alexander Monakov
2020-01-19 17:17 ` Alexander Monakov
2020-01-19 17:19 ` Rich Felker
2020-01-19 17:32 ` Alexander Monakov
2020-01-19 17:38 ` Rich Felker
2020-01-19 19:13 ` Alexander Monakov
2020-01-19 16:33 ` Alexander Cherepanov
2020-01-19 16:39 ` Rich Felker
2020-01-19 21:34 ` Alexander Cherepanov
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=d8bd0b30-d732-5926-9c37-3674ab241218@openwall.com \
--to=ch3root@openwall.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).