similar to: [LLVMdev] -Woverloaded-virtual

On Tuesday 16 May 2006 03:19, Chris Lattner wrote: > On Mon, 15 May 2006, Nai Xia wrote: > > > In other words, if I only use -steens-aa and the data_XXXs are all > > external global variables( and so inComplete ), > > Sounds right! > > > the call to printf will > > make the same effect, which I have tested it. > > > > Am I right ? :) >

Hi Chris, I took a haste look at the "Points-to Analysis in Almost Linear Time" by Steens , your PHD thesis and SteensGaard.cpp in LLVM this afternoon. So I think: 1. Actually the basic algorithm described originally by SteensGaard does not provide MOD/REF information for functions. 2. The context insensitive part of Data Structure Analysis (LocalAnalysis) can be deemed as an

Duncan, thanks for your answer! > In order to perform this transform the optimizers would have to work out > that sample does not modify any global state.  This cannot be done without > knowing the definition of sample, but you only provide a declaration. Which is why I am trying to supply this additional information in a custom alias analysis pass, but it doesn't seem to work. (The

On Mon, 15 May 2006, Nai Xia wrote: > In other words, if I only use -steens-aa and the data_XXXs are all > external global variables( and so inComplete ), Sounds right! > the call to printf will > make the same effect, which I have tested it. > > Am I right ? :) If you've tested it then, yes you're right :). I haven't played with this stuff for a long time,

I was reading the code in AliasAnalysis.cpp and happened to notice what looks like a bug. See the line marked by '*' below: AliasAnalysis::ModRefResult AliasAnalysis::getModRefInfo(const VAArgInst *V, const Location &Loc) { // If the va_arg address cannot alias the pointer in question, then the // specified memory cannot be accessed by the va_arg. if (!alias(getLocation(V),

I am getting -Werror failures building: [off-opt] : [llvm] /ptmp/dag/llvm/official/llvm/include/llvm/ADT/StringRef.h: In member function 'virtual llvm::AliasAnalysis::AliasResult {anonymous}::AliasAnalysisCounter::alias(const llvm::AliasAnalysis::Location&, const llvm::AliasAnalysis::Location&)': [off-opt] : [llvm]

Hi, I'm having a problem with GVN removing a load instruction that I think is needed. Dump before GVN: *** IR Dump Before Global Value Numbering *** ; Function Attrs: minsize optsize define i16 @TEST__MAIN(i16 %argc.13.par, i16** %argv.14.par) #0 { %buf.17 = alloca [10 x i16], align 1 %_tmp30 = getelementptr inbounds [10 x i16], [10 x i16]* %buf.17, i16 0, i16 0, !dbg !22 call

On Jun 29, 2010, at 9:59 AM, Will Dietz wrote: > Hi all, > > While working on a loadable Alias Analysis module pass, I'm running > into the following issue: > > I'm finding my pass queried for results after it has had > 'releaseMemory' called on it and its dependencies, but before > runOnModule is called again (on my pass or its deps). As you might >

Hi all, While working on a loadable Alias Analysis module pass, I'm running into the following issue: I'm finding my pass queried for results after it has had 'releaseMemory' called on it and its dependencies, but before runOnModule is called again (on my pass or its deps). As you might expect, this makes my pass rather unhappy (and I think correctly so). This happens with LICM

> On 2015-Jun-13, at 09:12, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Sat, Jun 13, 2015 at 12:52 AM, Chandler Carruth <chandlerc at gmail.com> wrote: > Greetings all, > > I'm working on refactoring the alias analysis layers to remove the usage of analysis groups and make the logic sharable between old and new pass managers, and I have a

I've long been an advocate of using -Woverloaded-virtual. The thing with this option is that it can REALLY help catch some nasty inheritance bugs. I'm running into these as I'm designing the bytecode analyzer interface. I make a change to the interface, forget to change a subclass, and bingo, that method doesn't get called any more and the compiler doesn't warn me about it. I

On Thu, 24 Jun 2004, Reid Spencer wrote: > I asked Chris about this months ago but there was little interest in > changing it. I thought we were talking about -Weffc++ at that time? > Perhaps we need to file a bug to take care of the warnings it produces > so that LLVm is overloaded virtual clean, then we can turn on checking > for overloaded virtuals. This sounds like a great

On Wed, Sep 9, 2009 at 11:49 PM, Mai, Haohui <haohui.mai at gmail.com> wrote: > On 9/9/09 3:28 AM, Eli Friedman wrote: >> On Wed, Sep 9, 2009 at 12:50 AM, Lei Shang<shang1982 at gmail.com>  wrote: >> >>> Hi, >>> >>>     I just found -steens-aa and -ds-aa Alias Analysis listed in documents do >>> not exist in my llvm-2.3 code. Both from

Greetings all, I'm working on refactoring the alias analysis layers to remove the usage of analysis groups and make the logic sharable between old and new pass managers, and I have a couple of questions below. As background, the overall plan that I've discussed with Hal and a few others previously is as follows: - Create an AliasAnalysisManager which is provided by a normal analysis

Hello, I'm playing with alias analysis, using the following program: %i = external global int ; <int*> [#uses=2] implementation ; Functions: int %_Z3bari(int %p) { entry: %tmp.0 = load int* %i ; <int> [#uses=1] %tmp.1 = setgt int %tmp.0, 10 ; <bool> [#uses=1] br bool %tmp.1, label %then, label %UnifiedReturnBlock then:

Hi ! I'm writting an AliasAnalysis using the online tutorial (http://www.llvm.org/docs/AliasAnalysis.html). My problem is to chain this pass (function Pass in my case) with the basicAA ... I know that my pass is running (runOnFunction) but the virtual methods derived from AliasAnalysis (alias, getModRefInfo, etc ... ) are never called (even in the case wherer the basicAA reaches the end

On Wed, 17 May 2006, Nai Xia wrote: > Unfortunately, I did not locate the lines in steens-aa for "printf" special case. > In ds-aa, I found the lines below: Right, steens-aa and ds-aa share code for "local analysis", they just stitch it together into an interprocedural analysis in different ways. The code below is used for steens-aa. >

Vikram S. Adve wrote: > On Feb 22, 2007, at 10:21 AM, Robert L. Bocchino Jr. wrote: > > >>I glanced at the code again, and it looks like I use DSA to (1) >>construct the call graph and (2) identify things that would be >>unsafe to put on the stack, such as arrays, cyclic data structures, >>and allocations with escaping references. Right now these parts

On Feb 22, 2007, at 1:54 PM, Nick Lewycky wrote: > Vikram S. Adve wrote: >> On Feb 22, 2007, at 10:21 AM, Robert L. Bocchino Jr. wrote: >> >> >>> I glanced at the code again, and it looks like I use DSA to (1) >>> construct the call graph and (2) identify things that would be >>> unsafe to put on the stack, such as arrays, cyclic data structures,

On 10/7/11 11:56 PM, Jiesheng Wei wrote: > Hi, > > This is Jiesheng Wei from UBC. Now I am working on a project with LLVM > and I want to use steensgaard alias analysis tool. I saw on the website > that steensgaard analysis is available for LLVM 2.9 and it is under > poolalloc/ directory. I downloaded several versions but none of them is > compatible with LLVM 2.9. Can you