Displaying 2 results from an estimated 2 matches for "c9a4fba4".
2019 Jun 06
2
@llvm.memcpy not honoring volatile?
...te; so I think this actually is a bug.
As the documentation says though, it's unwise to depend on the
behaviour of a volatile memcpy.
Cheers.
Tim.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190606/c9a4fba4/attachment.html>
2019 Jun 05
4
@llvm.memcpy not honoring volatile?
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 memcpy will access each byte exactly once. How is that useful?
I agree it's probably not that useful, but I think the non-duplicating
property of volatile is ingrained strongly enough that viewing a
memcpy as a single load and