[LLVMdev] where should volatileness really live in the AA API?

Krzysztof Parzyszek kparzysz at codeaurora.org
Wed Apr 1 03:39:15 PDT 2015


On 3/31/2015 5:41 PM, Daniel Berlin wrote:
>
> class Location is theoretically about pointers and sizes, but right
> now, our struct Location in AA already has metadata tags and other
> *instruction* specific info that it grabs from the instruction you
> pass to getLocation. IE it includes noalias data that it tries to
> match against other instructions.
> So we already have broken this abstraction to return better answers :)

Is it using anything other than alias-related metadata?  My view is that 
volatileness does not belong in the alias analysis.  Noalias metadata 
helps directly with what AA does, so it makes sense to have it there. 
Volatileness, not so much.

-Krzysztof

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, 
hosted by The Linux Foundation



More information about the llvm-dev mailing list