Displaying 14 results from an estimated 14 matches for "global_memori".
Did you mean:
global_memory
2013 Mar 21
2
[LLVMdev] How to describe a pointer that points to All memory(include global memory, heap, stack)?
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
2013 Mar 21
2
[LLVMdev] How to describe a pointer that points to All memory(include global memory, heap, stack)?
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:
2013 Mar 22
0
[LLVMdev] How to describe a pointer that points to All memory(include global memory, heap, stack)?
On Thu, Mar 21, 2013 at 12:29 AM, Steven Su <steven_known at yahoo.com.cn> wrote:
> 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
2013 Mar 21
0
[LLVMdev] How to describe a pointer that points to All memory(include global memory, heap, stack)?
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:
2013 Mar 13
0
[LLVMdev] How to describe a pointer that points to All memory(include global memory, heap, stack)?
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;
> }
>
2013 Mar 13
2
[LLVMdev] How to describe a pointer that points to All memory(include global memory, heap, stack)?
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
2013 Aug 08
5
[LLVMdev] Address space extension
On Aug 7, 2013, at 6:38 PM, Michele Scandale <michele.scandale at gmail.com> wrote:
> On 08/08/2013 03:16 AM, Pete Cooper wrote:
>>
>> On Aug 7, 2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com> wrote:
>>
>>> On 08/08/2013 02:02 AM, Justin Holewinski wrote:
>>>> This worries me a bit. This would introduce language-specific
2013 Aug 08
1
[LLVMdev] Address space extension
On Thu, Aug 08, 2013 at 08:05:33AM -0400, Justin Holewinski wrote:
> On Wed, Aug 7, 2013 at 9:52 PM, Pete Cooper <peter_cooper at apple.com> wrote:
>
> >
> > On Aug 7, 2013, at 6:38 PM, Michele Scandale <michele.scandale at gmail.com>
> > wrote:
> >
> > On 08/08/2013 03:16 AM, Pete Cooper wrote:
> >
> >
> > On Aug 7, 2013, at 5:12
2013 Aug 08
0
[LLVMdev] Address space extension
On 08/08/2013 03:52 AM, Pete Cooper wrote:
>> Why a backend should be responsible (meaning have knowledge) for a
>> mapping between high level address spaces and low level address spaces?
> Thats true. I’m thinking entirely from the persecutive of the backend
> doing CL/CUDA. But actually LLVM is language agnostic. That is still
> something the metadata could solve. The
2013 Aug 08
0
[LLVMdev] Address space extension
On Wed, Aug 7, 2013 at 9:52 PM, Pete Cooper <peter_cooper at apple.com> wrote:
>
> On Aug 7, 2013, at 6:38 PM, Michele Scandale <michele.scandale at gmail.com>
> wrote:
>
> On 08/08/2013 03:16 AM, Pete Cooper wrote:
>
>
> On Aug 7, 2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com>
> wrote:
>
> On 08/08/2013 02:02 AM, Justin
2013 Aug 08
1
[LLVMdev] Address space extension
On 08/08/2013 02:05 PM, Justin Holewinski wrote:
> On Wed, Aug 7, 2013 at 9:52 PM, Pete Cooper <peter_cooper at apple.com
> <mailto:peter_cooper at apple.com>> wrote:
>
>
> On Aug 7, 2013, at 6:38 PM, Michele Scandale
> <michele.scandale at gmail.com <mailto:michele.scandale at gmail.com>> wrote:
>
>> On 08/08/2013 03:16 AM, Pete
2013 Aug 08
0
[LLVMdev] Address space extension
On 08/08/2013 03:16 AM, Pete Cooper wrote:
>
> On Aug 7, 2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com> wrote:
>
>> On 08/08/2013 02:02 AM, Justin Holewinski wrote:
>>> This worries me a bit. This would introduce language-specific
>>> processing into SelectionDAG. OpenCL maps address spaces one way, other
>>> languages map them
2013 Aug 08
3
[LLVMdev] Address space extension
On Aug 7, 2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com> wrote:
> On 08/08/2013 02:02 AM, Justin Holewinski wrote:
>> This worries me a bit. This would introduce language-specific
>> processing into SelectionDAG. OpenCL maps address spaces one way, other
>> languages map them in other ways. Currently, it is the job of the
>> front-end to map
2013 Aug 08
4
[LLVMdev] Address space extension
On Aug 7, 2013, at 7:23 PM, Michele Scandale <michele.scandale at gmail.com> wrote:
> On 08/08/2013 03:52 AM, Pete Cooper wrote:
>>> Why a backend should be responsible (meaning have knowledge) for a
>>> mapping between high level address spaces and low level address spaces?
>> Thats true. I’m thinking entirely from the persecutive of the backend
>> doing