search for: stacksiz

...(AMD64 ABI 3.5.7 rule 10). Why this problem happened? When calling va_start to set va_list, overflow_arg_area is not set correctly. To set the overflow_arg_area correctly, we need to get the FrameIndex correctly. Now, here comes the problem, llvm doesn't handle it correctly. It accounts for StackSize to compute the FrameIndex, and if the StackSize is not aligned, it will compute the wrong FrameIndex. As a result overflow_arg_area will not be set correctly. My Solution: 1. Record the Align if it is located in Memory. 2. If it is variadic function and needs to set FrameIndex, adjust the stacksi...

...OMMAND 36032 root 2838 44 0 1917M 1493M ucond 0 406:39 3.03% CGServer ... $cat /boot/loader.conf.local ... kern.maxdsiz="1073741824" kern.maxssiz="134217728" kern.dfldsiz="1073741824" $limits Resource limits (current): ... datasize 1048576 kB stacksize 131072 kB How and why is it possible for process to grow up to 1493M and even more? I suppose, it will be able to eat all available system memory (was killed). Thank you for answers. -- Sincerely, Sergey Chumakov

...&& // No dynamic alloca. !MFI->adjustsStack() && // No calls. !IsWin64) { // Win64 has no Red Zone uint64_t MinSize = X86FI->getCalleeSavedFrameSize(); if (HasFP) MinSize += SlotSize; StackSize = std::max(MinSize, StackSize > 128 ? StackSize - 128 : 0); MFI->setStackSize(StackSize); } else if (IsWin64) { // We need to always allocate 32 bytes as register spill area. // FIXME: We might reuse these 32 bytes for leaf functions. StackSize += 32; MFI->setStackSi...

On Thu, Jul 18, 2013 at 10:31 PM, Yun-Wei Lee <lee2041412 at gmail.com> wrote: > Thank for your suggestion. > > I have tried to use GetAlignedArgumentStackSize. > It is so strange that this function may output uncorrectly. > For example, the StackSize will be 40 when handling the third function call > in main. > If I modified the this function, it will fail one test. > I wonder this may be another bug in llvm...... > And that's why...

hi all, the stacksize required for encoder and decoder are 32Kbytes and 16 Kbyes respectively. i changed it to 20Kbytess and 8Kbytes and it seems to work. but need to trim further. can someone point me in the right direction to further reducing the stack size? thanks! cheers, tk

I'm trying to insert some instructions before each function calls (before arguments push): lea %EAX, label ----- new instructions mov [ESP+stacksize], %EAX ----- new instructions push arg1 push arg2 ... push argn call callee_name I am a newbie to LLVM. I tried to use buildMI() to insert the instructions in the lowercall() function. But I couldn't put these instructions in the right positions. Is there a way to locate the p...

Hi all, today we've encountered quite strange issues with memory allocation on one of our VPS running CentOS 6.2. So far I've been unable to determine what's causing it - hopefully someone here will know what's up. The VPS is a "small" machine - just 512MB of RAM, 1 CPU, running 6.2. with current kernel (2.6.32-220.4.2.el6.x86_64, but I've tried the

...gt; For broader uses, the discussion is still open. > > To move forward on the diagnostic part, here is the plan: > - Extend the current handler with a prototype like: > void report(enum Kind, enum Classification, const char* msg) > where > - Kind is the kind of report: InlineAsm, StackSize, Other. > - Classification is Error, Warning. > - msg contains the fall back message to print in case the front-end do not know what to do with the report. Hello Quentin, could you explain how plugins would use your infrastructure? Would it be possible for a plugin to provide (limited) wa...

...8:02, "SHUCAI YAO via llvm-dev" <llvm-dev at lists.llvm.org> > wrote: > >> I'm trying to insert some instructions before each function calls (before >> arguments push): >> lea %EAX, label ----- new instructions >> mov [ESP+stacksize], %EAX ----- new instructions >> push arg1 >> push arg2 >> ... >> push argn >> call callee_name >> >> I am a newbie to LLVM. I tried to use buildMI() to insert the >> instructions in the lowercall() function. But I couldn't put th...

...* snip */ st = (EncState*)speex_alloc(sizeof(EncState)+8000*sizeof(spx_sig_t)); /* snip */ } same goes for the decoder: void *nb_decoder_init(const SpeexMode *m) { /* snip */ st = (DecState *)speex_alloc(sizeof(DecState)+4000*sizeof(spx_sig_t)); /* snip */ } I tried to reduce the stacksize from 8000/4000 to say 2000/1000, and reduce buffer size to 160 bytes: src/modes.c: /* Default mode for narrowband */ static const SpeexNBMode nb_mode = { 160, /*frameSize*/ 40, /*subframeSize*/ 10, /*lpcSize*/ 640, /*bufSize*/ <--------- reduce to 160 t...

...player diff --git a/libswfdec/swfdec_script.c b/libswfdec/swfdec_script.c index 2860e24..4b17af1 100644 --- a/libswfdec/swfdec_script.c +++ b/libswfdec/swfdec_script.c @@ -650,8 +650,16 @@ swfdec_action_call (JSContext *cx, guint JSStackFrame *fp = cx->fp; int i, j; jsval tmp; + guint stacksize; - g_assert ((guint) (fp->sp - fp->spbase) >= n_args + 2); + stacksize = fp->sp - fp->spbase; + g_assert (stacksize >= 2); + if (n_args + 2 > stacksize) { + SWFDEC_WARNING ("broken script. Want %u arguments, only got %u", n_args, stacksize - 2); + n_args...

...in this area in GCC in the past and I would prefer to > not repeat that experience with LLVM. > My technique was to log the stack size and build a bunch of code, and then analyze the logs before and after. It seemed really effective though? I also have some tests (sadly internal) that check stacksize is under some bound and those tend to serve is good indicators that something has gone badly wrong. For example, without the Clang tricks at -O0, we couldn't get their tests to pass. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/piper...

...read so far) rsync error: error in rsync protocol data stream (code 12) at /usr/common/src/rsync-2.5.6/io.c(165) However, rsync has only increased in resident size to about 72 MB at this point, while I have limits of: cputime unlimited filesize unlimited datasize 8192MB stacksize 1024MB coredumpsize unlimited resident 16033MB descriptors 4096 addressspace 8192MB Any comments? I have not seen anything in the archives that addresses this. Thanks, -smt

...ro. For example: func1(...) { ... } func2(...) { ... } Say the first function uses 64 bytes of the stack and an assumed offset of 0 and the second function uses 32 bytes of the stack but an assumed offset of 64. I've found out how to get the size of the stack via MachineFrameInfo.StackSize/getObjectSize, however I have not found out how to determine the starting offset of the stack for that specific function. I need this information so that I can offset my stack pointer correctly since all my indices into my stack need to start at 0 for each independent function call. So, what...

...formation emitted in an easily parsable way (e.g. in CSV form) , or will I need to add the capability? There is an optimization remark emitted (in YAML) for the stack size: $ clang -fsave-optimization-record foo.c $ cat foo.opt.yaml […] --- !Analysis Pass: prologepilog Name: StackSize DebugLoc: { File: foo.c, Line: 3, Column: 0 } Function: main Args: - NumStackBytes: '24' - String: ' stack bytes in function' ... […] For more information about optimization remarks I suggest Adam’s talk: https://llvm.org/devmtg/2016-11/Slides/Nemet-Co...

...Flag(MachineInstr::FrameSetup); +#else + // MOV64mr Reg, -SaveSize(%rbp) + addRegOffset(BuildMI(MBB, MBBI, DL, TII.get(X86::MOV64mr)), + FramePtr, true, -SaveSize) + .addReg(Reg) + .setMIFlag(MachineInstr::FrameSetup); +#endif + } + + StackSize += SaveSize; + MFI.setStackSize(StackSize); + } } // Mark the FramePtr as live-in in every block. Don't do this again for Index: lib/Target/X86/X86FrameLowering.h =================================================================== --- lib/Target/X86/X86FrameLowering.h (...

...---------------------------- Computer & software info: OS: kUbuntu Feasty Fawn 7.04 (64-bit) Processor: AMD Opteron 64-bit R: version 2.7.0 (64-bit) Cache memory: currently 16 GB (was 2 GB) Outcome of 'limit' command in shell: cputime unlimited, filesize unlimited, datasize unlimited, stacksize 8192 kbytes, coredumpsize 0 kbytes, memoryuse unlimited, vmemoryuse unlimited, descriptors 1024, memorylocked unlimited, maxproc unlimited ----------------------------------- a. We have recently upgraded the cache memory from 2 to 16 GB. However, we have noticed that somehow R still swaps memo...

...on.c:404) ==22369== by 0x113461: main (test-crypto.c:554) ==22369== If you believe this happened as a result of a stack ==22369== overflow in your program's main thread (unlikely but ==22369== possible), you can try to increase the size of the ==22369== main thread stack using the --main-stacksize= flag. ==22369== The main thread stack size used in this run was 8388608. Failed to run: ./test-crypto make[2]: *** [check-test] Error 1 make[2]: Leaving directory `/home/alice/rpmbuild/BUILD/dovecot-2.2.25/src/lib-dcrypt' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/h...

...discussion is still open. >> >> To move forward on the diagnostic part, here is the plan: >> - Extend the current handler with a prototype like: >> void report(enum Kind, enum Classification, const char* msg) >> where >> - Kind is the kind of report: InlineAsm, StackSize, Other. >> - Classification is Error, Warning. >> - msg contains the fall back message to print in case the front-end do not know what to do with the report. > > Hello Quentin, > > could you explain how plugins would use your infrastructure? I am not familiar with how plu...

I would like to be able to emit a list of functions by name and their fixed stack reservation size information, so that a programmer can gauge how much stack they are likely to need in tightly constrained embedded systems. Despite the rich number of options, the only option I can find that is even relatively close is: -warn-stack-size=<uint> Is there some existing way of getting this