diff options
author | Peter Collingbourne <peter@pcc.me.uk> | 2015-06-18 23:59:22 +0000 |
---|---|---|
committer | Peter Collingbourne <peter@pcc.me.uk> | 2015-06-18 23:59:22 +0000 |
commit | 9881b78b53dd295f7ee63bf33c99d68b73c2f289 (patch) | |
tree | 0c8f81af4719ee09af6acf7b09fc1a6854ed346f /llvm/lib/CodeGen/MachineModuleInfo.cpp | |
parent | c847e7e54372dd823264a1358a085c237baec8ed (diff) | |
download | llvm-9881b78b53dd295f7ee63bf33c99d68b73c2f289.zip llvm-9881b78b53dd295f7ee63bf33c99d68b73c2f289.tar.gz llvm-9881b78b53dd295f7ee63bf33c99d68b73c2f289.tar.bz2 |
Introduce -fsanitize-trap= flag.
This flag controls whether a given sanitizer traps upon detecting
an error. It currently only supports UBSan. The existing flag
-fsanitize-undefined-trap-on-error has been made an alias of
-fsanitize-trap=undefined.
This change also cleans up some awkward behavior around the combination
of -fsanitize-trap=undefined and -fsanitize=undefined. Previously we
would reject command lines containing the combination of these two flags,
as -fsanitize=vptr is not compatible with trapping. This required the
creation of -fsanitize=undefined-trap, which excluded -fsanitize=vptr
(and -fsanitize=function, but this seems like an oversight).
Now, -fsanitize=undefined is an alias for -fsanitize=undefined-trap,
and if -fsanitize-trap=undefined is specified, we treat -fsanitize=vptr
as an "unsupported" flag, which means that we error out if the flag is
specified explicitly, but implicitly disable it if the flag was implied
by -fsanitize=undefined.
Differential Revision: http://reviews.llvm.org/D10464
llvm-svn: 240105
Diffstat (limited to 'llvm/lib/CodeGen/MachineModuleInfo.cpp')
0 files changed, 0 insertions, 0 deletions