[cfe-dev] GSOC Static Analyzer Proposal

Magnus Reftel magnus.reftel at gmail.com
Thu Apr 11 01:37:57 PDT 2013


On 10 April 2013 19:54, John Regehr <regehr at cs.utah.edu> wrote:

> I would like to work on improving support for C++ in the static analyzer.
>> Specifically, I think it
>> would be valuable to improve the checkers for undefined behavior
>> including those already suggested.
>>
>
> I'd be happy to provide feedback on a more specific version of this part
> of the proposal.
>
> In particular, a useful starting point (maybe this already exists?) would
> be a list of all C/C++ undefined behaviors broken down by whether
> Clang/LLVM...
>
> - can reliably provide a compile-time diagnostic
>
> - can reliably provide a runtime diagnostic
>
> - cannot provide any diagnostic, but implements a predictable behavior
>
> - cannot provide any diagnostic and also implements unpredictable behavior
>
> Obviously the last category is the interesting place for future work.
>

A list of all undefined/implementation defined/unspecified behaviour in
ANSI-C and a classification of which can be determined statically and/or
dynamically can be found in Les Hatton's Safer C. Perhaps that could be of
help when examining where Clang is on those items?

Best Regards
Magnus Reftel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130411/db7bfdf4/attachment.html>


More information about the cfe-dev mailing list