[llvm-commits] [llvm] r113858 - in /llvm/trunk: include/llvm/Analysis/AliasAnalysis.h include/llvm/Analysis/LibCallAliasAnalysis.h include/llvm/Analysis/LibCallSemantics.h include/llvm/LLVMContext.h lib/Analysis/AliasAnalysis.cpp lib/Analysis/AliasAnalysisCounter.cpp lib/Analysis/AliasDebugger.cpp lib/Analysis/BasicAliasAnalysis.cpp lib/Analysis/IPA/GlobalsModRef.cpp lib/Analysis/LibCallAliasAnalysis.cpp lib/Analysis/ScalarEvolutionAliasAnalysis.cpp lib/Analysis/TypeBasedAliasAnalysis.cpp lib/VMCore/LLVMContext.cpp

[Chris Lattner]

On Sep 16, 2010, at 5:15 PM, Dan Gohman wrote:
On Sep 15, 2010, at 6:24 PM, Chris Lattner wrote:
> 
>> On Sep 14, 2010, at 2:25 PM, Dan Gohman wrote:
>>> 
>>> +    explicit Location(const Value *P = 0,
>> 
>> Should the pointer be allowed to be null?  Is Location() something that is useful?
> 
> It's convenient, though not necessary.

Sure, I'm asking whether you think it is the "right" thing for the API.  I'm not challenging your decision, just making sure you thought about it.  Previously, the pointer provided to alias() was not allowed to be null.

-Chris