[llvm-bugs] [Bug 34399] New: StaticAnalyzer/Core/ExprEngine.cpp UNREACHABLE executed

[via llvm-bugs]

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

            Bug ID: 34399
           Summary: StaticAnalyzer/Core/ExprEngine.cpp UNREACHABLE
                    executed
           Product: clang
           Version: trunk
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Static Analyzer
          Assignee: kremenek at apple.com
          Reporter: chh at google.com
                CC: llvm-bugs at lists.llvm.org

Created attachment 19073
  --> https://bugs.llvm.org/attachment.cgi?id=19073&action=edit
preprocessed p.cpp and command in run.sh

The attached p.zip contains a test case that
shows an assertion failure triggered by core
static analyzer checks.

To reproduce the problem:
(1) build clang-tidy with assertion check.
(2) run the run.sh script.

The assertion failure is:
  Support for this Decl not implemented.
  UNREACHABLE executed at
.../llvm/tools/clang/lib/StaticAnalyzer/Core/ExprEngine.cpp:2087!

The p.cpp is preprocessed file from Android Open Source.
The compilation mode -std=gnu++1z is needed to reproduce the error.

Several Android source files have this problem and they are compiled
with -std=gnu++1z. If there is some gnu features not supported by
static analyzer, can static analyzer skip them gracefully?

If we can identify the source syntax, maybe we can avoid them in the source.

-- 
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/20170831/6326eefa/attachment.html>