diff options
| author | Alexey Samsonov <vonosmas@gmail.com> | 2015-06-25 23:14:32 +0000 |
|---|---|---|
| committer | Alexey Samsonov <vonosmas@gmail.com> | 2015-06-25 23:14:32 +0000 |
| commit | 9b87309a9144e7dde65edb2425380f008af02afc (patch) | |
| tree | 3ef7f0ee4a7b1232eddbdf639b15296926cc746d /llvm/lib/Object/Error.cpp | |
| parent | 5aecacb275d1e0d1bcc59f6b3a3596c1a8a500d9 (diff) | |
| download | llvm-9b87309a9144e7dde65edb2425380f008af02afc.zip llvm-9b87309a9144e7dde65edb2425380f008af02afc.tar.gz llvm-9b87309a9144e7dde65edb2425380f008af02afc.tar.bz2 | |
[CFI] Diagnose when we CFI in diagnostic mode is unavailable on a toolchain.
Summary:
Namely, we must have proper C++ABI support in UBSan runtime. We don't
have a good way to check for that, so just assume that C++ABI support is
there whenever -fsanitize=vptr is supported (i.e. only on handful of
platforms).
Exact diagnostic is also tricky. It's not "cfi" that is unsupported,
just the diagnostic mode. So, I suggest to report that
"-fno-sanitize-trap=cfi-foobar" is incompatible with a given target
toolchain.
Test Plan: regression test suite
Reviewers: pcc
Subscribers: cfe-commits
Differential Revision: http://reviews.llvm.org/D10751
llvm-svn: 240716
Diffstat (limited to 'llvm/lib/Object/Error.cpp')
0 files changed, 0 insertions, 0 deletions