From: Jordan Rose Date: Sat, 5 Apr 2014 06:10:22 +0000 (+0000) Subject: [analyzer] Update Open Projects page with BitwiseConstraintManager. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=333e7cfe8f338a367941c6423ffc10eda8893028;p=clang [analyzer] Update Open Projects page with BitwiseConstraintManager. Also, add the names of people most recently working on particular projects, and remove "relate bugs and checkers" (thanks, Alex!). git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@205666 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/www/analyzer/open_projects.html b/www/analyzer/open_projects.html index 4a888adbb6..75c069260c 100644 --- a/www/analyzer/open_projects.html +++ b/www/analyzer/open_projects.html @@ -56,7 +56,7 @@ mailing list to notify other members of the community.

  • Enhance CFG to model C++ temporaries properly.

    There is an existing implementation of this, but it's not complete and is disabled in the analyzer. - (Difficulty: Medium)

    + (Difficulty: Medium; current contact: Alex McCarthy)

  • Enhance CFG to model exception-handling properly.

    Currently exceptions are treated as "black holes", and exception-handling @@ -70,7 +70,7 @@ mailing list to notify other members of the community.

    (operator new), then initialize the result with a constructor call. The problem is discussed at length in PR12014. - (Difficulty: Easy)

    + (Difficulty: Easy; current contact: Karthik Bhat)

  • Enhance CFG to model C++ delete more precisely.

    Similarly, the representation of delete does not include @@ -78,7 +78,14 @@ mailing list to notify other members of the community.

    function (operator delete). One particular issue (noreturn destructors) is discussed in PR15599 - (Difficulty: Easy)

    + (Difficulty: Easy; current contact: Karthik Bhat)

    + +
  • Implement a BitwiseConstraintManager to handle PR3098. +

    Constraints on the bits of an integer are not easily representable as + ranges. A bitwise constraint manager would model constraints such as "bit 32 + is known to be 1". This would help code that made use of bitmasks. + (Difficulty: Medium)

    +
  • Track type info through casts more precisely.

    The DynamicTypePropagation checker is in charge of inferring a region's @@ -107,14 +114,6 @@ mailing list to notify other members of the community.

    display such paths in HTML output. (Difficulty: Medium)

  • -
  • Relate bugs to checkers / "bug types" -

    We need to come up with an API which will relate bug reports - to the checkers that produce them and refactor the existing code to use the - new API. This would allow us to identify the checker from the bug report, - which paves the way for selective control of certain checks. - (Difficulty: Easy-Medium)

    -
  • -
  • Refactor path diagnostic generation in BugReporter.cpp.

    It would be great to have more code reuse between "Minimal" and "Extensive" PathDiagnostic generation algorithms. One idea is to create an @@ -182,7 +181,7 @@ mailing list to notify other members of the community.

    Take a look at the CP-Miner paper for inspiration. - (Difficulty: Medium-Hard)

    + (Difficulty: Medium-Hard; current contacts: Per Viberg and Daniel Fahlgren)