search for: bigstack

Hello LLVMDev, I've encountered what looks like a bug in LLVM 2.9, it doesn't appear to be fixed in 3.0 either. The problem occurs in function ARMFrameLowering.cpp:processFunctionBeforeCalleeSavedScan. There's a circular dependency in setting the variable BigStack and AFI->setHashStackFrame(true). The expression which initializes BigStack calls estimateRSSStackSizeLimit which in turn checks AFI->hasStackFrame(). Unfortunately setHasStackFrame(true) only gets called after BigStack is initialized. The specific issue this caused in my case was that BigSt...

Hi, attached is a second try for the bigstack patch for SPU, with testcase. It is essentially the patch committed as 97091, and reverted as 97099, but with the following additions: -in vararg handling, registers are marked to be live, to not confuse the register scavenger -function prologue and epilogue are not emitted, if the stack size is...

Hello Alok, > I fixed this by performing the CanEliminateFrame and > RegInfo->cannotEliminateFrame checks before the call to > estimateRSSStackSizeLimit, since these values are available before BigStack > is initialized. Does that sound reasonable? I’ve attached a patch with my > change. Will you please provide a testcase which reproduces the problem? Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

...edu Subject: Re: [LLVMdev] bug in ARMFrameLowering.cpp:processFunctionBeforeCalleeSavedScan Hello Alok, > I fixed this by performing the CanEliminateFrame and > RegInfo->cannotEliminateFrame checks before the call to > estimateRSSStackSizeLimit, since these values are available before BigStack > is initialized. Does that sound reasonable? I’ve attached a patch with my > change. Will you please provide a testcase which reproduces the problem? Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University __________________...

...y enabled in SPURegisterInfo::requiresRegisterScavenging(const MachineFunction &MF). Just checking MF.getFrameInfo()->getStackSize() here doesn't seem to be the solution... kalle -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: bigstack.ll URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100226/2e97950d/attachment.ksh>

On Mar 29, 2010, at 6:50 AM, Kalle Raiskila wrote: > attached is a second try for the bigstack patch for SPU, with testcase. It is essentially the patch committed as 97091, and reverted as 97099, but with the following additions: > -in vararg handling, registers are marked to be live, to not confuse the register scavenger Looks good. You can try running with -verify-machineinstrs to dete...

On Feb 22, 2010, at 6:08 AM, Kalle.Raiskila at nokia.com wrote: > Hello all, > > currently the SPU backend does not handle big stack frames (>16*511 > bytes) nicely. llc asserts on malformed machine instructions. > (Assertion `MI->getOperand(OpNo).isImm() && "printDFormAddr first > operand is not immediate") Sounds fine to me in general. Please write a

Hello all, currently the SPU backend does not handle big stack frames (>16*511 bytes) nicely. llc asserts on malformed machine instructions. (Assertion `MI->getOperand(OpNo).isImm() && "printDFormAddr first operand is not immediate") E.g. the function: define i32 @foo() nounwind { entry: %retval = alloca i32 %big_data = alloca [1000 x i32] store i32 3840, i32*

...ion/C/2004-03-15-IndirectGoto SingleSource/Regression/C/2005-05-06-LongLongSignedShift SingleSource/Regression/C/2008-01-07-LongDouble SingleSource/Regression/C++/2008-01-29-ParamAliasesReturn SingleSource/Regression/C++/2011-03-28-Bitfield SingleSource/Regression/C/badidx SingleSource/Regression/C/bigstack SingleSource/Regression/C++/BuiltinTypeInfo SingleSource/Regression/C/callargs SingleSource/Regression/C/casts SingleSource/Regression/C/compare SingleSource/Regression/C/ConstructorDestructorAttributes SingleSource/Regression/C/DuffsDevice SingleSource/Regression/C++/EH/class_hierarchy SingleSourc...

...ke comparing to plain -O3), there are a significant number of compile-time speedups (I guess that this is because vectorization can reduce the number of instructions processed by later passes). Top compile-time speedups: SingleSource/Benchmarks/Stanford/Oscar - 46% speedup SingleSource/Regression/C/bigstack - 45% speedup SingleSource/Benchmarks/BenchmarkGame/fannkuch - 45% speedup > >> Interesting. Do you understand what causes these slowdowns? Can your > >> heuristic be improved? > > > > I've not specifically looked at these cases. > > > > Generally, I...

...ngleSource/UnitTests/SignlessTypes/rem | * | * | SingleSource/Regression/C/pointer_arithmetic | * | * | SingleSource/Regression/C/2003-05-22-VarSizeArray | * | * | SingleSource/Regression/C/bigstack | * | * | SingleSource/Regression/C/badidx | * | * | SingleSource/Regression/C/uint64_to_float | * | * | SingleSource/Regression/C/test_indvars...

On 11/08/2011 03:36 PM, Hal Finkel wrote: > On Tue, 2011-11-08 at 12:12 +0100, Tobias Grosser wrote: >> On 11/08/2011 11:45 AM, Hal Finkel wrote: >>> I've attached the latest version of my autovectorization patch. >>> >>> Working through the test suite has proved to be a productive >>> experience ;) -- And almost all of the bugs that it revealed

On Tue, 2011-11-08 at 12:12 +0100, Tobias Grosser wrote: > On 11/08/2011 11:45 AM, Hal Finkel wrote: > > I've attached the latest version of my autovectorization patch. > > > > Working through the test suite has proved to be a productive > > experience ;) -- And almost all of the bugs that it revealed have now > > been fixed. There are still two programs that

...0.00 * 0.01 | - - n/a n/a SingleSource/Regression/C/badidx | 0.0034 848 0.0043 * 0.0041 | 0.00 0.00 0.00 * 0.00 | - - n/a n/a SingleSource/Regression/C/bigstack | 0.0172 3328 0.0153 * 0.0147 | 0.00 0.00 0.00 * 0.02 | - - n/a n/a SingleSource/Regression/C/callargs | 0.0031 884 0.0035 * 0...

...0.00 * 0.02 | - - n/a n/a SingleSource/Regression/C/badidx | 0.0040 888 0.0080 * 0.0000 | 0.00 0.00 0.00 * 0.02 | - - n/a n/a SingleSource/Regression/C/bigstack | 0.0160 3312 0.0080 * 0.0120 | 0.00 0.00 0.00 * 0.03 | - - n/a n/a SingleSource/Regression/C/callargs | 0.0000 884 0.0040 * 0...

LLVMers, The 2.2 prerelease is now available for testing: http://llvm.org/prereleases/2.2/ If anyone can help test this release, I ask that you do the following: 1) Build llvm and llvm-gcc (or use a binary). You may build release (default) or debug. You may pick llvm-gcc-4.0, llvm-gcc-4.2, or both. 2) Run 'make check'. 3) In llvm-test, run 'make TEST=nightly report'. 4) When

...0.00 * 0.02 | - - n/a n/a SingleSource/Regression/C/badidx | 0.0089 880 0.0041 * 0.0040 | 0.00 0.00 0.00 * 0.02 | - - n/a n/a SingleSource/Regression/C/bigstack | 0.0197 3300 0.0138 * 0.0125 | 0.00 0.00 0.00 * 0.02 | - - n/a n/a SingleSource/Regression/C/callargs | 0.0037 880 0.0070 * 0...

...0.00 * 0.01 | - - n/a n/a SingleSource/Regression/C/badidx | 0.0016 908 0.0021 * 0.0021 | 0.00 0.00 0.00 * 0.00 | - - n/a n/a SingleSource/Regression/C/bigstack | 0.0066 3160 0.0066 * 0.0067 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a SingleSource/Regression/C/callargs | 0.0014 912 0.0021 * 0...

...      0.02 | -       -       n/a          n/a > SingleSource/Regression/C/badidx                                         | > 0.0100 1012     0.0000      *                0.0000      |    0.00    0.00 >  0.00 *           0.01 | -       -       n/a          n/a > SingleSource/Regression/C/bigstack                                       | > 0.0000 4820     0.0200      *                0.0100      |    0.00    0.00 >  0.00 *           0.03 | -       -       n/a          n/a > SingleSource/Regression/C/callargs                                       | > 0.0000 928      0.0100      *  ...

Hi Tanya, > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a > pre-compiled llvm-gcc or re-compile it yourself. I compiled llvm and llvm-gcc with separate objects directories. Platform is x86_64-linux-gnu. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to