search for: r42525

...from the caller function parameters and would be overwritten if they are not moved. In cases where they would not be overwritten they could be directly lowered to the real stack slot). regards arnold -------------- next part -------------- A non-text attachment was scrubbed... Name: tailcall-r42525-src.patch Type: application/octet-stream Size: 60519 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20071002/da888d9c/attachment.obj>

On Tue, 25 Sep 2007, Evan Cheng wrote: >> the stack adjustment only fastcc was not one of them. Now that fastcc >> can cause tail call optimization i had to change the convention from >> caller pops arguments to callee pops arguments in order to allow tail >> call optimization in a general way. > > Hmmm. Ok. So this is due to X86CallingConv.td changes? Unfortunately

...In cases where they would not be overwritten > they could be directly lowered to the real stack slot). Please add the potential optimizations (with concrete examples / assembly snippets) to README.txt under Target/X86. Thanks! Evan > > > regards arnold > > > <tailcall-r42525- > src.patch>_______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

...oking whether the actual > parameters come from the caller function parameters and would be > overwritten if they are not moved. In cases where they would not be > overwritten they could be directly lowered to the real stack slot). > > regards arnold > > > <tailcall-r42525- > src.patch>_______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev