search for: addrspacesdescriptor

...TargetData and create a specific subclass for our compiler, when I discovered that this is not how TargetData is supposed to work. Currently, TargetData consists only of a TargetDescription, which is basically only sizes and alignment info for different types. I solved this by creating a new class AddrspacesDescriptor, which has a single virtual method that defines the relationship between address spaces. This class contains a default implementation and can be subclassed to get a different implementation. A reference to a AddrspaceDescriptor is passed to TargetData's constructor, with a default. This means...

...ormation we need, I think you have it right. We just need a description of how the different address spaces relate and I don't see much of an issue with how you implemented to InstructionCombining. As you also mentioned, I don't like that we pass a reference to TargetData with the AddrspacesDescriptor and that we have a static default implementation store in the class. It is unclear to me if this is the right class for it as not as it describes the structure and alignment while address spaces seems distinct from that. I feel that this information should be part of the TargetMachine as...

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

Hi Mon Ping, > As you also mentioned, I don't like that we pass a reference to > TargetData with the AddrspacesDescriptor and that we have a static > default implementation store in the class. It is unclear to me if > this is the right class for it as not as it describes the structure > and alignment while address spaces seems distinct from that. I feel > that this information should be part of t...

On 2008-07-21, at 14:42, Matthijs Kooijman wrote: > Hi Mon Ping, > >> As you also mentioned, I don't like that we pass a reference to >> TargetData with the AddrspacesDescriptor and that we have a static >> default implementation store in the class. It is unclear to me if >> this is the right class for it as not as it describes the structure >> and alignment while address spaces seems distinct from that. I >> feel that this information sho...