Displaying 2 results from an estimated 2 matches for "cncolc".
Did you mean:
ccol
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
2019 Jun 06
2
@llvm.memcpy not honoring volatile?
...the explanation Eli and Tim.
My understanding of volatile was that you may have a different value every time you read and as such overlapping reads may be a bug.
Now, since the behaviour of volatile memcpy is not guaranteed and since clang does not allow to use it anyways<https://godbolt.org/z/CnCOLc> I would like to challenge its existence.
Is there a know reason for keeping the volatile argument in @llvm.memcpy?
On Wed, Jun 5, 2019 at 11:28 PM Tim Northover <t.p.northover at gmail.com<mailto:t.p.northover at gmail.com>> wrote:
On Wed, 5 Jun 2019 at 13:49, Eli Friedman via llv...