search for: pointerabialign

...rspace2) const { + return Equivalent; + } + + virtual ~AddrspacesDescriptor() {} +}; + class TargetData : public ImmutablePass { private: bool LittleEndian; ///< Defaults to false unsigned char PointerMemSize; ///< Pointer size in bytes unsigned char PointerABIAlign; ///< Pointer ABI alignment unsigned char PointerPrefAlign; ///< Pointer preferred alignment + const AddrspacesDescriptor &Addrspaces; ///< Address spaces descriptor + static const AddrspacesDescriptor DefaultAddrspaces; ///< Default address spaces descriptor //...

...t; + } > + > + virtual ~AddrspacesDescriptor() {} > +}; > + > class TargetData : public ImmutablePass { > private: > bool LittleEndian; ///< Defaults to false > unsigned char PointerMemSize; ///< Pointer size in bytes > unsigned char PointerABIAlign; ///< Pointer ABI alignment > unsigned char PointerPrefAlign; ///< Pointer preferred > alignment > + const AddrspacesDescriptor &Addrspaces; ///< Address spaces > descriptor > + static const AddrspacesDescriptor DefaultAddrspaces; ///< Default &gt...

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