Displaying 7 results from an estimated 7 matches for "ramptr".
2007 Sep 13
0
[LLVMdev] PointerTypes with AddressSpace
...r 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
> generalPtr = ramPtr; // non resolvable conflict
> }
This basically amounts to type inference. If you want this, it would
have to be implemented in the front-end, not in at the LLVM level
(you lose too much to give useful error reports etc).
Type inference is very nice, but it is not in the spirit of C at
a...
2007 Sep 13
2
[LLVMdev] PointerTypes with AddressSpace
...r 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
> generalPtr = ramPtr; // non resolvable conflict
> }
This basically amounts to type inference. If you want this, it would
have to be implemented in the front-end, not in at the LLVM level
(you lose too much to give useful error reports etc).
Type inference is very nice, but it is not in the spirit of C at
a...
2007 Sep 13
3
[LLVMdev] PointerTypes with AddressSpace
...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
generalPtr = ramPtr; // non resolvable conflict
}
-- d) Conflicts at the function interface will spawn a new function
eg:
void inc(int *a){
(*a)++;
}
void g(void){
inc(romPointer); // this will spawn an f with rom pointer
inc(ramPointer); // this will spawn an f with ram pointer
}
In the case of (2) we s...
2007 Sep 13
0
[LLVMdev] PointerTypes with AddressSpace
...ter
>> 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
>> generalPtr = ramPtr; // non resolvable conflict
>> }
>
> This basically amounts to type inference. If you want this, it would
> have to be implemented in the front-end, not in at the LLVM level
> (you lose too much to give useful error reports etc).
>
> Type inference is very nice, but it is n...
2007 Sep 14
2
[LLVMdev] Embedded C Language Extensions
...ter
>> 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
>> generalPtr = ramPtr; // non resolvable conflict
>> }
>
> This basically amounts to type inference. If you want this, it would
> have to be implemented in the front-end, not in at the LLVM level
> (you lose too much to give useful error reports etc).
>
> Type inference is very nice, but it is n...
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