From acdb4b920351b13c23b3795fe00079a8f8f4bff8 Mon Sep 17 00:00:00 2001 From: Eric Christopher Date: Sat, 17 Jul 2010 00:25:41 +0000 Subject: [PATCH] Make comment a bit more clear as well as return statement since needsStackRealignment is currently checking the can conditions as well. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@108581 91177308-0d34-0410-b5e6-96231b3b80d8 --- lib/Target/X86/X86RegisterInfo.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/Target/X86/X86RegisterInfo.cpp b/lib/Target/X86/X86RegisterInfo.cpp index a5134b857e4..0703bdb7bb5 100644 --- a/lib/Target/X86/X86RegisterInfo.cpp +++ b/lib/Target/X86/X86RegisterInfo.cpp @@ -462,12 +462,12 @@ bool X86RegisterInfo::needsStackRealignment(const MachineFunction &MF) const { // FIXME: Currently we don't support stack realignment for functions with // variable-sized allocas. - // FIXME: Temporary disable the error - it seems to be too conservative. + // FIXME: It's more complicated than this... if (0 && requiresRealignment && MFI->hasVarSizedObjects()) report_fatal_error( "Stack realignment in presense of dynamic allocas is not supported"); - return (requiresRealignment && !MFI->hasVarSizedObjects()); + return requiresRealignment && canRealignStack(MF); } bool X86RegisterInfo::hasReservedCallFrame(MachineFunction &MF) const { -- 2.34.1