search for: getaddrspacerelation

...y->getElementType(), SrcTy->getAddressSpace()); + + // Only propagate the address space when the source and dest address spaces + // are equivalent, or the source address space is a subset of the target + // address space. + AddrspacesDescriptor::AddrspaceRelation Rel; + Rel = TD->getAddrspaceRelation(SrcTy->getAddressSpace(), + DestTy->getAddressSpace()); + if (Rel != AddrspacesDescriptor::Equivalent + && Rel != AddrspacesDescriptor::Subset) + return 0; + + // We can propagate the address space if we can modify the type of CI. This + //...

...ressSpace()); > + > + // Only propagate the address space when the source and dest > address spaces > + // are equivalent, or the source address space is a subset of the > target > + // address space. > + AddrspacesDescriptor::AddrspaceRelation Rel; > + Rel = TD->getAddrspaceRelation(SrcTy->getAddressSpace(), > + DestTy->getAddressSpace()); > + if (Rel != AddrspacesDescriptor::Equivalent > + && Rel != AddrspacesDescriptor::Subset) > + return 0; > + > + // We can propagate the address space if we can modif...

Hi Eli, Mon Ping, > In ISO/IEC WG14 n1169 on the C extensions to support embedded > processors, any two address spaces must be disjoint, must be > equivalent, or must be nested. Ah, that standard is a lot clearer on this subject than the DSP-C one I read was. > As Eli indicated, the actual relationship is platform specific depending on > what makes the most sense for

In ISO/IEC WG14 n1169 on the C extensions to support embedded processors, any two address spaces must be disjoint, must be equivalent, or must be nested. As Eli indicated, the actual relationship is platform specific depending on what makes the most sense for your hardware and how the program will behave will depend on that relationship. -- Mon Ping On Jul 17, 2008, at 7:25 AM, Eli