search for: thestruct

Dan, thanks for your hints about the post-RA scheduler. However, I have difficulties creating a reasonably small and concise testcase for the problem I described, and it's on my own target anyway. In principle, I see the following: %theStruct = type { %theStruct2, %theStruct3, i16, ... } define void @f1(%theStruct* %tmp) { // initialize some locals %a= alloca i16, align 2 store i16 1, i16* %a ;similar b ... . . // GEP some pointers to elements of tmp %x = getelementptr %theStruct* %tmp, i64 0, i32 13 ; similiar y,z... . . ca...

On Mar 25, 2009, at 11:21 AM, Christian Sayer wrote: > Hi all, > for my target, the register allocator tends to make use of few (i.e. > it seems one single) registers when allocating stack slots to > registers. This happens only to function locals (allocas) - > allocation for e.g. function arguments passed by the stack work fine. > For example, the debug output of the

Hi all, for my target, the register allocator tends to make use of few (i.e. it seems one single) registers when allocating stack slots to registers. This happens only to function locals (allocas) - allocation for e.g. function arguments passed by the stack work fine. For example, the debug output of the initialization of several stack slots is the following: 1 : entry: 2 :