Constraints. These concepts are already present in the current ValueState, but
the implementation is monolothic. Making ValueState more modular opens up new
design choices for customizing the analysis engine.

In the context of the analysis engine, the "Environment" is the binding between
Expr* (expressions) and intermediate symbolic values (RValues).

llvm-svn: 53252

llvm-svn: 53250

llvm-svn: 53248

llvm-svn: 53238

llvm-svn: 53235

llvm-svn: 53234

llvm-svn: 53233

llvm-svn: 53222

llvm-svn: 53221

llvm-svn: 53219

llvm-svn: 53216

llvm-svn: 53191

In a report-XXXXX.html, make the title include the name of the file with the bug.  Patch by Jean-Daniel Dupas!

http://lists.cs.uiuc.edu/pipermail/cfe-dev/2008-July/002166.html

llvm-svn: 53184

Mark the "Bug Type" column as being initially sorted (display the sort ding) so that users can readily see that the table can be sorted.

llvm-svn: 53176

llvm-svn: 53175

also fix the correspondent test (it was expecting more errors than it should. please confirm my fix is correct (at least gcc agrees with me)

llvm-svn: 53174

llvm-svn: 53172

llvm-svn: 53170

This patch aims to address some of the concerns of PR 2517: http://llvm.org/bugs/show_bug.cgi?id=2517

llvm-svn: 53168

llvm-svn: 53160

llvm-svn: 53149

llvm-svn: 53145

llvm-svn: 53144

llvm-svn: 53143

llvm-svn: 53141

llvm-svn: 53140

This was broken when the GenerateCode function was splitted to use GenerateFunction.

llvm-svn: 53136

'&&' commands together so that the test status reflects the results of all the commands, otherwise the test status will be the result of only the last command.

llvm-svn: 53135

llvm-svn: 53133

'&&' clang commands together so that the test status reflects the results of all three clang executions.

llvm-svn: 53132

llvm-svn: 53129

passed-by-reference to a function. This allows us to build up constraints for
their new values and restore some lost path-sensitivity. This addresses a few
false positives since in Adium.

llvm-svn: 53125

llvm-svn: 53121

llvm-svn: 53118

  http://lists.cs.uiuc.edu/pipermail/cfe-dev/2008-July/002157.html

Essentially the observer mechanism in LiveVariables was observing block-level
expressions multiple times, leading to a case where the dead store checker could
see a value as dead when it was really live.

llvm-svn: 53115

llvm-svn: 53114

llvm-svn: 53107

llvm-svn: 53103

llvm-svn: 53100

llvm-svn: 53099