Re: about named address space

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 27, 2011 at 4:51 PM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote:
> Rony Paul <ronypaul77@xxxxxxxxx> writes:
>
>> suppose I have the following piece of code in my program.
>>
>>   extern  int __ea x;
>>   int y;
>>   y = x;
>>
>> that means I am copying data from one address space to another.
>> in that case will the method spu_addr_space_convert (rtx op, tree
>> from_type, tree to_type);  be called by the compiler?
>> in the spu.c file the defination of " spu_addr_space_convert " is
>> given. but when and under which condition they will be called ?
>
> I'm pretty sure it won't be called.  That function converts a pointer to
> one address space into a pointer to a different address space.  No such
> conversion is happening here.
>
>> where
>> is it defined?
>
> The function spu_addr_space_convert is the SPU-specific implementation
> of the target hook TARGET_ADDR_SPACE_CONVERT which is documented in the
> section on named address spaces.
>
> Ian
>


Then if I want to prevent these type of copying data from one address
space to another (ie. I dont want to allow these type of copy
operation in my application). where should I write code in GCC
compiler?

Actually I can define different address space, but still I cant store
there data in different byte order. would you give me any idea about
how to store data in different byte order in different address space?

-Rony
 please suggest me,



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux