search for: allocainstr

...ff> Twine <http://llvm.org/docs/doxygen/html/classllvm_1_1Twine.html> Name <http://llvm.org/docs/doxygen/html/SymbolizableObjectFile_8cpp.html#ab104eb44fb0574709f0ceb43b50bdb63> allocaI); // InsertBefore Presently I am passing previous allocaInstr Poiter as last argument as i shown above So New allocaInstr is inserting before previous allocaInstr in LLVM IR as follows output %p1 = alloca i32*, align 8 // New Alloca Instrctions %b = alloca i32, align 4 // previous Alloca Instrctions how can I get output like below %b = alloca i32, alig...

...6. I noticed there are a few bugs outstanding on the issue. I recently added some code which had the effect of throwing an extra function parameter on our stack at runtime, a 4 byte pointer. Esp is now not 16-byte aligned, so instructions like unpcklps xmm1, dword ptr [eps] cause grief. My AllocaInstr instructions are told to be 16 byte aligned, so the addition of a 4-byte parameter shouldn't have changed alignment on the objects. The unpcklps instruction is coming from an ExtractElementInst or InsertElementInst. I can always hard code these by cyling my vectors to memory and doing thin...

...few bugs outstanding on the issue. I recently added > some code which had the effect of throwing an extra function > parameter on our stack at runtime, a 4 byte pointer. > > Esp is now not 16-byte aligned, so instructions like unpcklps xmm1, > dword ptr [eps] cause grief. My AllocaInstr instructions are told > to be 16 byte aligned, so the addition of a 4-byte parameter > shouldn’t have changed alignment on the objects. Hi Chuck, I think the basic problem is that the stack pointer on windows/linux is not guaranteed to be 16 byte aligned. This means that any use of...

...est>clang test.ll -o test.exe E:\test>test.exe values : n2 = 16, dna = 0, dnb = 10 n2, dna and dnb are respectively the three i32 variables. Does anyone know how to fix this? Alignment attribute on the variadic function do nothing and the VAArgInst does not support setAlignment() like the AllocaInstr. During my research, I found that when a VAArgInst is being lowered in SelectionDAG::expandVAARG(), the alignment information is retrieved from the va_arg SDNode and the lowering is wrong (in this case). The alignment is set in SelectionDAGBuilder::visitVAArg() where it creates a VAArg DAG using...

...est>clang test.ll -o test.exe E:\test>test.exe values : n2 = 16, dna = 0, dnb = 10 n2, dna and dnb are respectively the three i32 variables. Does anyone know how to fix this? Alignment attribute on the variadic function do nothing and the VAArgInst does not support setAlignment() like the AllocaInstr. During my research, I found that when a VAArgInst is being lowered in SelectionDAG::expandVAARG(), the alignment information is retrieved from the va_arg SDNode and the lowering is wrong (in this case). The alignment is set in SelectionDAGBuilder::visitVAArg() where it creates a VAArg DAG using...