Displaying 2 results from an estimated 2 matches for "p1152r0".
Did you mean:
p1152r1
2019 Jun 11
3
@llvm.memcpy not honoring volatile?
...developers here.
Volatile isn’t specified in any decent normative way. There’s substantial documentation of intent, but C and C++ standards are lacking. We should therefore implement something that’s sensible and works kind-of as expected.
I’ve documented specification and intent here: wg21.link/P1152R0 <http://wg21.link/P1152R0>
If you want to follow-on (without all that documentation): wg21.link/P1152R1 <http://wg21.link/P1152R1>
I think we want option 2.: keep volatile memcpy, and implement it as touching each byte exactly once. That’s unlikely to be particularly useful for every d...
2019 Jun 10
2
@llvm.memcpy not honoring volatile?
I agree, this is a bug.
John
On 6/7/19 11:48 AM, JF Bastien via llvm-dev wrote:
>
>
>> On Jun 5, 2019, at 2:28 PM, Tim Northover via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>
>> On Wed, 5 Jun 2019 at 13:49, Eli Friedman via llvm-dev
>> <llvm-dev at lists.llvm.org> wrote:
>>> I don’t see any particular reason to guarantee that a volatile