Revision cbaebc0a5c48d5cf2bec46fc270e5aac4f36e0b0 authored by Dan Gohman on 06 March 2014, 02:49:30 UTC, committed by Dan Gohman on 06 March 2014, 02:49:30 UTC
This testcase was originally inspired by libgcrypt. Compiling
asm("":::"memory") to a no-op would be doable, and would help the code
compile without error, but properly supporting what libgrypt is actually
doing here, being paranoid enough to make repeated stores to the same
memory location to clear it out, would be much harder, because we'd
really need a way to tell the JS engine what's going on so that it doesn't
optimize anything away.
1 parent 28f0397
CONTRIBUTING.md
Contributing
============
See our wiki for information about contributing to Emscripten:
[Contribution section on wiki](https://github.com/kripken/emscripten/wiki#contributing)
Computing file changes ...
