Displaying 2 results from an estimated 2 matches for "20181230041359if_".
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
2019 Jun 11
3
@llvm.memcpy not honoring volatile?
> On Jun 11, 2019, at 6:27 AM, Guillaume Chatelet <gchatelet at google.com> wrote:
>
> I spent some time reading the C standard <https://web.archive.org/web/20181230041359if_/http://www.open-std.org/jtc1/sc22/wg14/www/abq/c17_updated_proposed_fdis.pdf>:
>
> 5.1.2.3 Program execution
> 2. Accessing a volatile object, modifying an object, modifying a file, or calling a function that does any of those operations are all side effects, which are changes in the s...