search for: addrspace2

...{ +public: + typedef enum { + Equivalent, + Disjoint, + Subset, + Superset + } AddrspaceRelation; + + /// getAddrspaceRelation - Returns the relation between the given address + /// spaces. Should be read left to right, for example Subset means that + /// Addrspace1 is a subset of Addrspace2. + virtual AddrspaceRelation getAddrspaceRelation( + int Addrspace1, + int Addrspace2) const { + return Equivalent; + } + + virtual ~AddrspacesDescriptor() {} +}; + class TargetData : public ImmutablePass { private: bool LittleEndian; ///< Defaults to false...

...Disjoint, > + Subset, > + Superset > + } AddrspaceRelation; > + > + /// getAddrspaceRelation - Returns the relation between the given > address > + /// spaces. Should be read left to right, for example Subset > means that > + /// Addrspace1 is a subset of Addrspace2. > + virtual AddrspaceRelation getAddrspaceRelation( > + int Addrspace1, > + int Addrspace2) const { > + return Equivalent; > + } > + > + virtual ~AddrspacesDescriptor() {} > +}; > + > class TargetData : public ImmutablePass { > private: > bool...

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