search for: propagateaddressspace

...ning.cpp (revision 53716) +++ lib/Transforms/Scalar/InstructionCombining.cpp (working copy) @@ -400,6 +400,8 @@ unsigned GetOrEnforceKnownAlignment(Value *V, unsigned PrefAlign = 0); + /// Propagate address spaces through bitcasts + Instruction *PropagateAddressSpace(BitCastInst &CI); }; } @@ -7841,6 +7843,81 @@ return 0; } +/// Try to propagate the address space from the source of the bitcast into all +/// of its uses. CI casts between two pointer types with different address spaces. +Instruction *InstCombiner::PropagateAddressSpace(BitCastInst...

...+++ lib/Transforms/Scalar/InstructionCombining.cpp (working copy) > @@ -400,6 +400,8 @@ > unsigned GetOrEnforceKnownAlignment(Value *V, > unsigned PrefAlign = 0); > > + /// Propagate address spaces through bitcasts > + Instruction *PropagateAddressSpace(BitCastInst &CI); > }; > } > > @@ -7841,6 +7843,81 @@ > return 0; > } > > +/// Try to propagate the address space from the source of the > bitcast into all > +/// of its uses. CI casts between two pointer types with different > address spaces. > +Inst...

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