search for: manchanda

Displaying 5 results from an estimated 5 matches for "manchanda".

Did you mean: kanchana
2011 Dec 05
1
[LLVMdev] bug in ARMFrameLowering.cpp:processFunctionBeforeCalleeSavedScan
...om elsewhere in the file. Anton, would you agree with this? I haven't looked at ARMFrameLowering before. Cheers, James -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Anton Korobeynikov Sent: 05 December 2011 11:11 To: Alok Manchanda Cc: llvmdev at cs.uiuc.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 valu...
2011 Jun 02
1
Help in a project
...hrough this: my attempt to this was : l=0 # placeholder m<-c() #newvariable 1 v<-c() #newvariable flag for (z in tablename1$Variable_1) (if (is.numeric(z) ) m[z:l] l=l+1 else v[z:1] l=l+1 Can you please guide me as to how to approach this problem? Any help would be greatly appreciated. Tarun Manchanda [[alternative HTML version deleted]]
2011 Dec 05
0
[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
2011 Dec 05
2
[LLVMdev] bug in ARMFrameLowering.cpp:processFunctionBeforeCalleeSavedScan
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
2010 Sep 15
1
specs inside subfolder of lib folder not displaying proper error messages
hi im facing this issue in which if i place a failing spec inside a subfolder of my lib folder then along with the error message the file name and the line number is not shown. output as below: ''Test one'' FAILED expected: 2, got: 1 (using ==) but if i move the spec directly under lib or any other folder then i see the file name and line number with error message as below