Displaying 5 results from an estimated 5 matches for "maxalign".
Did you mean:
max_align
2006 Oct 06
0
[LLVMdev] should PEI::calculateFrameObjectOffsets align the stack?
On Fri, 6 Oct 2006, [UTF-8] Rafael Esp?ndola wrote:
> In ARM the stack should be 8 bytes aligned during function calls. A
> function that has at least one function call then has a stack size of
> 8 bytes. PEI::calculateFrameObjectOffsets corretly computes this
> correctly.
>
> The problem is that the alignment is computed before adding space for
> the call frame size. This is
2006 Oct 06
2
[LLVMdev] should PEI::calculateFrameObjectOffsets align the stack?
In ARM the stack should be 8 bytes aligned during function calls. A
function that has at least one function call then has a stack size of
8 bytes. PEI::calculateFrameObjectOffsets corretly computes this
correctly.
The problem is that the alignment is computed before adding space for
the call frame size. This is done in emitProlog. Currently the ARM
backend has a bug in that it doesn't align
2006 Oct 07
2
[LLVMdev] should PEI::calculateFrameObjectOffsets align the stack?
...ubs around calls. In
the PPC backend we have:
----------------------------------------------------------------------
if (MFI->hasCalls()) {
NumBytes += MFI->getMaxCallFrameSize();
}
if ((NumBytes == 0) || (NumBytes <= 224 && !HasFP && !MFI->hasCalls()
&& MaxAlign <= TargetAlign)) {
MFI->setStackSize(0);
return;
}
unsigned Align = std::max(TargetAlign, MaxAlign);
unsigned GPRSize = 4;
unsigned Size = HasFP ? GPRSize + GPRSize : GPRSize;
NumBytes = (NumBytes+Size+Align-1)/Align*Align;
---------------------------------------------------...
2011 Mar 09
1
[LLVMdev] TargetData::getPreferredAlignment(const GlobalVariable *GV) is strange ...
On Mar 9, 2011, at 8:40 AM, Duncan Sands wrote:
> Hi Fabian,
>
>> I am somewhat confused by the following method within the LLVM,
>> especially the lines
>> "confusion starts" -> "confusion ends" are hard to follow.
>
> yes, this seems like a wart. It has been there ever since Chris added the
> getPreferredAlignmentLog method in commit
2014 Nov 03
8
[LLVMdev] [PATCH] Protection against stack-based memory corruption errors using SafeStack
...gt;::iterator It = Returns.begin(),
+ Ie = Returns.end(); It != Ie; ++It) {
+ IRB.SetInsertPoint(*It);
+ IRB.CreateStore(BasePointer, UnsafeStackPtr);
+ }
+
+ // Compute maximum alignment among static objects on the unsafe stack
+ unsigned MaxAlignment = 0;
+ for (SmallVectorImpl<AllocaInst*>::iterator It = StaticAlloca.begin(),
+ Ie = StaticAlloca.end(); It != Ie; ++It) {
+ AllocaInst *AI = *It;
+ Type *Ty = AI->getAllocatedType();
+ unsigned Align =
+ std::max((unsigned)...