[llvm-bugs] [Bug 33201] New: Apple Clang bundled with Xcode 8 does not reject -fsanitize=undefined when it should

via llvm-bugs llvm-bugs at lists.llvm.org
Sun May 28 15:13:28 PDT 2017


https://bugs.llvm.org/show_bug.cgi?id=33201

            Bug ID: 33201
           Summary: Apple Clang bundled with Xcode 8 does not reject
                    -fsanitize=undefined when it should
           Product: clang
           Version: 3.8
          Hardware: Macintosh
                OS: MacOS X
            Status: NEW
          Severity: normal
          Priority: P
         Component: Frontend
          Assignee: unassignedclangbugs at nondot.org
          Reporter: noloader at gmail.com
                CC: llvm-bugs at lists.llvm.org

We are testing with the Undefined Behavior sanitizer on Travis CI. Travis
provides OS X with Xcode 8.2.

Our build results in (https://travis-ci.org/noloader/cryptopp/jobs/236976227):

ld: file not found:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/8.0.0/lib/darwin/libclang_rt.ubsan_osx_dynamic.dylib

clang: error: linker command failed with exit code 1 (use -v to see invocation)

make: *** [cryptest.exe] Error 1


If Clang cannot compile/link a program with Undefined Behavior sanitizer, then
it should reject -fsanitize=undefined and fail the compile.

We cannot use -fsanitize=address,undefined because Address Santizier has some
bugs, and it produces incorrect results with GCC inline assembly when ebp/rbp
is used as a general purpose register. Effectively we had to suspend Asan
testing and only use Valgrind.

-----

My apologies for filing an Apple Clang bug in the LLVM bug tracker. We don't
have an iTunes account, so this is the only way we know to bring it to the
Apple developers attention.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170528/20aa3b32/attachment.html>


More information about the llvm-bugs mailing list