Displaying 7 results from an estimated 7 matches for "addsp".
Did you mean:
adds
2007 Sep 13
0
[LLVMdev] PointerTypes with AddressSpace
...ecide its Address Space
> based
> on the following criteria? (we should be able to do so in an LLVM pass
> because at code generation time we have the full view of the program)
> -- a) Address Space of the pointer is the Address Space of the
> variable
> eg: ptr = &var; //AddSp of ptr becomes AddSp of var
> -- b) Address Space of the pointer is the address Space of the pointer
> eg: ptr1 = ptr2; //AddSp of ptr1 becomes AddSp of ptr2
> -- c) Conflicts inside functions are not resolvable and should
> generate
> diagnostic.
> eg:
> void f(void){
>...
2007 Sep 13
2
[LLVMdev] PointerTypes with AddressSpace
...ecide its Address Space
> based
> on the following criteria? (we should be able to do so in an LLVM pass
> because at code generation time we have the full view of the program)
> -- a) Address Space of the pointer is the Address Space of the
> variable
> eg: ptr = &var; //AddSp of ptr becomes AddSp of var
> -- b) Address Space of the pointer is the address Space of the pointer
> eg: ptr1 = ptr2; //AddSp of ptr1 becomes AddSp of ptr2
> -- c) Conflicts inside functions are not resolvable and should
> generate
> diagnostic.
> eg:
> void f(void){
>...
2007 Sep 13
3
[LLVMdev] PointerTypes with AddressSpace
...way to code generation, and then decide its Address Space based
on the following criteria? (we should be able to do so in an LLVM pass
because at code generation time we have the full view of the program)
-- a) Address Space of the pointer is the Address Space of the variable
eg: ptr = &var; //AddSp of ptr becomes AddSp of var
-- b) Address Space of the pointer is the address Space of the pointer
eg: ptr1 = ptr2; //AddSp of ptr1 becomes AddSp of ptr2
-- c) Conflicts inside functions are not resolvable and should generate
diagnostic.
eg:
void f(void){
generalPtr = romPtr;
//some code...
2007 Sep 13
0
[LLVMdev] PointerTypes with AddressSpace
...pace
>> based
>> on the following criteria? (we should be able to do so in an LLVM pass
>> because at code generation time we have the full view of the program)
>> -- a) Address Space of the pointer is the Address Space of the
>> variable
>> eg: ptr = &var; //AddSp of ptr becomes AddSp of var
>> -- b) Address Space of the pointer is the address Space of the pointer
>> eg: ptr1 = ptr2; //AddSp of ptr1 becomes AddSp of ptr2
>> -- c) Conflicts inside functions are not resolvable and should
>> generate
>> diagnostic.
>> eg:
>...
2007 Sep 14
2
[LLVMdev] Embedded C Language Extensions
...pace
>> based
>> on the following criteria? (we should be able to do so in an LLVM
pass
>> because at code generation time we have the full view of the program)
>> -- a) Address Space of the pointer is the Address Space of the
>> variable
>> eg: ptr = &var; //AddSp of ptr becomes AddSp of var
>> -- b) Address Space of the pointer is the address Space of the
pointer
>> eg: ptr1 = ptr2; //AddSp of ptr1 becomes AddSp of ptr2
>> -- c) Conflicts inside functions are not resolvable and should
>> generate
>> diagnostic.
>> eg:
>...
2007 Sep 12
0
[LLVMdev] New to LLVM, Help needed
On Wed, 12 Sep 2007 Alireza.Moshtaghi at microchip.com wrote:
> Thank you Chris,
> I had the pointer size wrong. I fixed it and now it passes that point as
> expected :) which takes me to a second question:
cool
> The processor that I am working on is 8-bit and has Harvard
> architecture; this implies different pointer types (sizes) to objects in
> data memory or program memory
2007 Sep 12
2
[LLVMdev] New to LLVM, Help needed
Thank you Chris,
I had the pointer size wrong. I fixed it and now it passes that point as
expected :) which takes me to a second question:
The processor that I am working on is 8-bit and has Harvard
architecture; this implies different pointer types (sizes) to objects in
data memory or program memory (functions or data in program memory)
At this moment, I am just using only one pointer size