[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <98d2e82c-1930-5dc2-2afa-bf6f4c9a8a50@gmail.com>
Date: Thu, 6 Jul 2017 21:05:12 +0200
From: Bartosz Brachaczek <b.brachaczek@...il.com>
To: musl@...ts.openwall.com
Subject: Re: Documentation of memcpy and undefined behavior in memset
On 7/6/2017 6:23 PM, Rich Felker wrote:
> I think you're correct, at least under a pessimistic interpretation of
> the standard. I can't find where they actually define "modifies", and
> you could argue that assignment of the same value twice "modifies" the
> object at most once, but I don't like relying on that kind of
> ambiguity and it's easy enough to fix just by adding a sequence point.
I don't have a copy of C11, but N1570 reads in a note to 3.1:
> ‘‘Modify’’ includes the case where the new value being stored is the same as the previous value.
Bartosz
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
