Displaying 3 results from an estimated 3 matches for "auto_upgrade_intrinsics".
2013 Jan 31
0
[LLVMdev] Specify the volatile access behaviour of the memcpy, memmove and memset intrinsics
...emcpy-memmove-set-volatile-on-the-source-or-destina.patch
implements this second step. It requires clang tests to be patched with
clang-0001-Update-checks-to-take-into-account-the-changes-on-th.patch as
the codegen'd memcpy / memmove will use the new format.
Finally, 0003-Upgrade-all-tests-but-auto_upgrade_intrinsics-to-use.patch
is purely mechanical : it upgrades all llvm tests (but
auto_upgrade_intrinsics :)) to use the new format for memcpy/memmove.
There are no functional changes, "make check-llvm check-clang" pass
after each patch is applied.
When those patches are accepted, I will commit them...
2013 Feb 03
0
[LLVMdev] Specify the volatile access behaviour of the memcpy, memmove and memset intrinsics
...le-on-the-source-or-destina.patch
> implements this second step. It requires clang tests to be patched with
> clang-0001-Update-checks-to-take-into-account-the-changes-on-th.patch as
> the codegen'd memcpy / memmove will use the new format.
>
> Finally, 0003-Upgrade-all-tests-but-auto_upgrade_intrinsics-to-use.patch
> is purely mechanical : it upgrades all llvm tests (but
> auto_upgrade_intrinsics :)) to use the new format for memcpy/memmove.
>
> There are no functional changes, "make check-llvm check-clang" pass
> after each patch is applied.
>
> When those patches...
2013 Jan 28
4
[LLVMdev] Specify the volatile access behaviour of the memcpy, memmove and memset intrinsics
Hi All,
In the language reference manual, the access behavior of the memcpy,
memmove and memset intrinsics is not well defined with respect to the
volatile flag. The LRM even states that "it is unwise to depend on it".
This forces optimization passes to be conservatively correct and prevent
optimizations.
A very simple example of this is :
$ cat test.c
#include <stdint.h>