[cfe-commits] r91535 - in /cfe/trunk: include/clang/Analysis/PathSensitive/GRExprEngine.h include/clang/Analysis/PathSensitive/MemRegion.h include/clang/Analysis/PathSensitive/Store.h lib/Analysis/GRExprEngine.cpp lib/Analysis/MemRegion.cpp lib/A

Zhongxing Xu xuzhongxing at gmail.com
Mon Dec 21 17:23:12 PST 2009


My main concern is that SymbolicRegion carries another sense that the
region may be NULL. But temporaries can't be NULL. We have to add an
Assume() to tell that to the analyzer.

2009/12/22 Ted Kremenek <kremenek at apple.com>:
> Could we use a SymbolicRegion for temporaries as well?  We currently
> associate many symbols with specific expressions, and can distinguish
> different symbolic values for the same expression along different loop
> iterations.
>
> On Dec 20, 2009, at 10:41 PM, Zhongxing Xu <xuzhongxing at gmail.com> wrote:
>
>> 2009/12/17 Ted Kremenek <kremenek at apple.com>:
>>>
>>> Hi Zhongxing,
>>>
>>> How do we plan on using CXXObjectRegion?
>>>
>>> For stack allocated objects, we will use VarRegions.  For heap allocated
>>> (e.g., 'new'), we will use SymbolicRegions.  For fields that are C++ objects
>>> we will use FieldRegions.
>>
>>
>> I got another potential usage for CXXObjectRegion: for
>> CXXTemporaryObjectExpr. It's not a varregion, not a symbolic region.
>




More information about the cfe-commits mailing list