search for: maydefs

Hi, John I am building a flow sensitive intra-procedural alias analysis(without interprocedural info). So, the first thing I have to consider is where a parameter-pointer or a global-pointer might point to. Then I defined several special Virtual Memory Locations: ALL_MEMORY, GLOBAL_MEMORY, STACK_MEMORY, HEAP_MEMORY. ALL_MEMORY contains GLOBAL_MEMORY, STACK_MEMORY, HEAP_MEMORY. e.g1:

Hi, Daniel, thank you for your advice. Yes, ALL_MEMORY points to ALL_MEMORY. We use MD(memory descriptor) to abstract a memory location.  MD contains 4 main fields: id, base, offset, size. For these special MD (ALL_MEMORY, GLOBAL_MEMORY, STACK_MEMORY, HEAP_MEMORY),  we give them id 1, 2, 3, 4, that means MD1 is ALL_MEMORY, MD2 is GLOBAL_MEMORY, the same goes for the rest.  Then we maintain a

...;s not strictly necessary, but it's not bad or harmful. > How to describe both MayDef, MayUse info if just have a single BITSET in each stmt? Cut the universe in half. Assuming 64 bit ids: bits 1-9223372036854775808 represent mayuses bits 9223372036854775809-18446744073709551616 represent maydefs (If your bitsets are sparse, and allow negative indexes, like gcc's, you could just use positive and negative numbers). This would need to be abstracted properly so that the union/intersect/diff/iterators operated only on the proper portions of the bitset. I'm not sure why you'd want...

On Wed, Mar 20, 2013 at 7:33 PM, Steven Su <steven_known at yahoo.com.cn> wrote: > Hi, John > I am building a flow sensitive intra-procedural alias analysis(without interprocedural info). > So, the first thing I have to consider is where a parameter-pointer or a global-pointer might point to. > Then I defined several special Virtual Memory Locations:

On 3/13/13 4:06 AM, Steven Su wrote: > Hello, could any one point me following question. Without any context, your question is difficult to answer. Are you building a points-to analysis and wanting to know how an alias analysis might encode the fact that a pointer could alias any other pointer? -- John T. > > e.g: > void foo(int * p) > { > *p = 0; > } >

Hello, could any one point me following question. e.g: void foo(int * p) { *p = 0; } Here 'p' may point to all memory location. Could you tell me how to represent the POINT TO set of 'p'? Here is my solution: Introduce a memory-class named: Global_Mem, then p pointed to global_mem. And the MOD set of '*p=0' is

On Feb 28, 2008, at 10:43 AM, Richard Warburton wrote: > This email is written on the premise that LLVM will be involved in > GSOC again this year. I hope so too! > I would be looking to implement a context-sensitive alias analysis. > Whilst I accept that this isn't the most efficient category of alias > analysis, I think the implementation of such an analysis, that trades

> Ok. I think the most important thing to keep in mind, if you want > this to be useful for LLVM, is for it to be sound in the presence of > incomplete programs. I think it would be very interesting to have a > BDD based analysis in LLVM, it would be useful for performance > comparisons and many other things, even if it isn't turned on by > default. However, it must

This email is written on the premise that LLVM will be involved in GSOC again this year. I noted that the wiki's open projects page [0] has several possible projects, that seem suitable for a summer of code project. I am writing this email to this list with the hope of getting some feedback on specifics for a GSOC application, and also wondering if any potential mentors are interested in