search for: e04b4d41

...rnaud A. de Grandmaison -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Specify-the-access-behaviour-of-the-memcpy-memmove-a.patch Type: text/x-patch Size: 7384 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130203/e04b4d41/attachment.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-memcpy-memmove-set-volatile-on-the-source-or-destina.patch Type: text/x-patch Size: 22970 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130203/e04b...

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>