[LLVMdev] updated code size comparison
regehr at cs.utah.edu
Wed Jan 20 20:21:46 PST 2010
> Right now it only catches out of range shifts and simple array out of
> bound issues, not all undefined behavior.
Besides the obvious memory safety stuff, my list of top undefined
behaviors to catch would be:
- multiple updates to objects between sequence points
- integer overflows
- use-after-death of stack variables
- use of uninitialized stack variables
- const/volatile violations
Some of these will be no fun to implement. But the resulting tool would
be enormously valuable.
More information about the llvm-dev