[hwasan] Remove lazy thread-initialisation
authorDavid Spickett <david.spickett@arm.com>
Mon, 4 Nov 2019 10:58:46 +0000 (10:58 +0000)
committerDavid Spickett <david.spickett@arm.com>
Mon, 4 Nov 2019 10:58:46 +0000 (10:58 +0000)
commit91167e22eca535025f093335acece573bf19c525
treede2c0f091bb043f125a31b5c4bcac91bf5241e16
parentbc728d584242946ba59d6bea0cf8c749dcf07248
[hwasan] Remove lazy thread-initialisation

This was an experiment made possible by a non-standard feature of the
Android dynamic loader.

It required introducing a flag to tell the compiler which ABI was being
targeted.
This flag is no longer needed, since the generated code now works for
both ABI's.

We leave that flag untouched for backwards compatibility. This also
means that if we need to distinguish between targeted ABI's again
we can do that without disturbing any existing workflows.

We leave a comment in the source code and mention in the help text to
explain this for any confused person reading the code in the future.

Patch by Matthew Malcomson

Differential Revision: https://reviews.llvm.org/D69574
clang/include/clang/Driver/Options.td
compiler-rt/lib/hwasan/hwasan_interceptors.cpp
compiler-rt/lib/hwasan/hwasan_linux.cpp
llvm/lib/Transforms/Instrumentation/HWAddressSanitizer.cpp
llvm/test/Instrumentation/HWAddressSanitizer/lazy-thread-init.ll [deleted file]