[llvm-dev] RFC: New function attribute HasInaccessibleState

Philip Reames via llvm-dev llvm-dev at lists.llvm.org
Fri Dec 4 10:38:06 PST 2015

On 12/04/2015 10:33 AM, Hal Finkel via llvm-dev wrote:
> ----- Original Message -----
>> From: "Vaivaswatha Nagaraj" <vn at compilertree.com>
>> To: "James Molloy" <james at jamesmolloy.co.uk>, "Hal Finkel" <hfinkel at anl.gov>
>> Cc: "LLVM Dev" <llvm-dev at lists.llvm.org>
>> Sent: Friday, December 4, 2015 12:28:03 PM
>> Subject: Re: [llvm-dev] RFC: New function attribute HasInaccessibleState
>> that would be an escaping global, and as far as I know is handled
>> separately in GlobalsAA (AnalyzeUsesOfPointer checks if a global is
>> used as operand to a function)
> More generally, I think this attribute is supposed to mean, "this function might access globals, but none of these globals are things you can name in the IR being optimized." You might, of course, pass in aliasing memory as a parameter, but that's a separate matter.
The general notion that Hal expressed here would be of interest to me as 
well.  I haven't read through the entire thread to form an opinion on 
how best to represent such a thing.


More information about the llvm-dev mailing list