Displaying 5 results from an estimated 5 matches for "globalvariabls".
Did you mean:
globalvariable
2008 Jul 22
0
[LLVMdev] LICM/store-aliasing of global loads
...r alias anything. That's a little
sneaky though, so offhand I think an approach such as what's in
your patch is better.
> If I apply the patch found further down, LICM moves the loads out (as
> expected), but of course this is a fairly specific fix.
Slightly better than checking for GlobalVariabls directly
is to call the AliasAnalysis' pointsToConstantMemory method.
BasicAliasAnalysis' implementation of that does exactly the same thing,
checking for constant GlobalVariables, but it would allow alias
analyses to do more sophisticated things. Could you submit a patch
for this?
> Wh...
2008 Jul 21
6
[LLVMdev] LICM/store-aliasing of global loads
Our frontend can guarantee that loads from globals are
rematerializable and do not alias with any stores in any function in
the given module. We'd like the optimization passes (and ideally the
register allocator as well) to be able to use this fact. The globals
are not constant "forever" but are constant during the calling of any
given function in the module.
There seem to
2008 Jul 22
3
[LLVMdev] LICM/store-aliasing of global loads
...ing to suggest that at least getModRefInfo should handle this
for stores, but it looks like it already does.
>> If I apply the patch found further down, LICM moves the loads out (as
>> expected), but of course this is a fairly specific fix.
>
> Slightly better than checking for GlobalVariabls directly
> is to call the AliasAnalysis' pointsToConstantMemory method.
> BasicAliasAnalysis' implementation of that does exactly the same
> thing,
> checking for constant GlobalVariables, but it would allow alias
> analyses to do more sophisticated things. Could you submit...
2016 Aug 04
3
help please: how to sort the contents of a "SymbolTableListTraits<GlobalVariable>"?
On 08/04/2016 01:33 PM, David Majnemer wrote:
> You should never be copying or moving around Values.
Why not? Is that because of this thing you also wrote in the same message: "use lists are
allocated before the object"?
> An llvm::Value (which GlobalVariable is a subtype of) should exist only in the heap.
Trying to sort a container of such objects doesn`t require me to
2008 Jul 23
0
[LLVMdev] LICM/store-aliasing of global loads
...51 PM, Stefanus Du Toit wrote:
> On 22-Jul-08, at 1:22 PM, Dan Gohman wrote:
>>> If I apply the patch found further down, LICM moves the loads out
>>> (as
>>> expected), but of course this is a fairly specific fix.
>>
>> Slightly better than checking for GlobalVariabls directly
>> is to call the AliasAnalysis' pointsToConstantMemory method.
>> BasicAliasAnalysis' implementation of that does exactly the same
>> thing,
>> checking for constant GlobalVariables, but it would allow alias
>> analyses to do more sophisticated things...