tree 136c834c21113b108fbcb07025ae14aa90f364bb
parent df60aeb2667e140a6c6ae93e9e1d8eb3d33d72ab
author Eric <eric@efcs.ca> 1521843047 -0600
committer GitHub <noreply@github.com> 1521843047 -0600
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJatXtnCRBK7hj4Ov3rIwAAdHIIAD4repICiYw8geHvv8I1vz4h
 Rts2YdLHfxnEuO206Stxc6V543qZvNoa7lXOM+G5OhiAKjrrRZcbVgfx8rdPch7C
 yTFOp0aMeCKUGzUHD2XUrUfOAE1ho2OCQzIWRzZoPlgEMai49eLBJBuS8ob03b7i
 ucEkoSyxtpm0SMLSoJcv4Q5bBT94+TK1dvce0VomnFBAeUy62tMFiIzgN4xYCXrx
 eydSUXII4/QCE3buJNzlMs0Ae+ox7EUwNpD1TE1iVoiz3kXI82QMsuRpNDyAV7BJ
 DZzgIwCoL1Nvb5ZTazFS6ka5NBmcrYQ9r1PGpXNDY2r189tbB5pV9QZ1a8IZ0V4=
 =jcZs
 -----END PGP SIGNATURE-----
 

Add tests to verify assembler output -- Fix DoNotOptimize. (#530)

* Add tests to verify assembler output -- Fix DoNotOptimize.

For things like `DoNotOptimize`, `ClobberMemory`, and even `KeepRunning()`,
it is important exactly what assembly they generate. However, we currently
have no way to test this. Instead it must be manually validated every
time a change occurs -- including a change in compiler version.

This patch attempts to introduce a way to test the assembled output automatically.
It's mirrors how LLVM verifies compiler output, and it uses LLVM FileCheck to run
the tests in a similar way.

The tests function by generating the assembly for a test in CMake, and then
using FileCheck to verify the // CHECK lines in the source file are found
in the generated assembly.

Currently, the tests only run on 64-bit x86 systems under GCC and Clang,
and when FileCheck is found on the system.

Additionally, this patch tries to improve the code gen from DoNotOptimize.
This should probably be a separate change, but I needed something to test.

* Disable assembly tests on Bazel for now

* Link FIXME to github issue

* Fix Tests on OS X

* fix strip_asm.py to work on both Linux and OS X like targets