[LLVMbugs] [Bug 24285] New: Sanitizer options are spelled differently between gcc and clang

[bugzilla-daemon at llvm.org]

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

            Bug ID: 24285
           Summary: Sanitizer options are spelled differently between gcc
                    and clang
           Product: clang
           Version: 3.6
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Driver
          Assignee: unassignedclangbugs at nondot.org
          Reporter: jonathan at codesourcery.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

gcc5 trunk expects the spelling: `-fsanitize=undefined
-fsanitize-undefined-trap-on-error`
whereas clang's spelling of that option is: `-fsanitize=undefined-trap
-fsanitize-undefined-trap-on-error`.

I don't know which one is the "correct" spelling, but the fact that they are
different and that clang doesn't accept the gcc spelling is a "clang isn't a
drop-in replacement for gcc" bug.

-- 
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/20150727/785295f6/attachment.html>