search for: argoffset

...ch/x86_64/kernel/entry-xen.S 2008-10-24 11:32:19.000000000 +0200 +++ head-2008-10-24/arch/x86_64/kernel/entry-xen.S 2008-10-24 11:33:13.000000000 +0200 @@ -121,9 +121,9 @@ NMI_MASK = 0x80000000 .macro CFI_DEFAULT_STACK start=1,adj=0 .if \start CFI_STARTPROC simple - CFI_DEF_CFA rsp,SS+8-(\adj*ARGOFFSET) + CFI_DEF_CFA rsp,SS+8 - \adj*ARGOFFSET .else - CFI_DEF_CFA_OFFSET SS+8-(\adj*ARGOFFSET) + CFI_DEF_CFA_OFFSET SS+8 - \adj*ARGOFFSET .endif .if \adj == 0 CFI_REL_OFFSET r15,R15 @@ -133,20 +133,20 @@ NMI_MASK = 0x80000000 CFI_REL_OFFSET rbp,RBP CFI_REL_OFFSET rbx,RBX .endif - CFI_REL_O...

...s.push_back(DAG.getStore(Chain, Arg, PtrOff, NULL, 0)); + if (!isTailCall) + MemOpChains.push_back(DAG.getStore(Chain, Arg, PtrOff, NULL, 0)); + // Calculate and remember argument location. + else + CalculateTailCallArgDest(DAG, MF, isPPC64, Arg, SPDiff, ArgOffset, + TailCallArguments); + inMem = true; } if (inMem || isMachoABI) { @@ -1994,7 +2339,13 @@ SDOperand PPCTargetLowering::LowerCALL(SDOperand Op, SelectionDAG &DAG, } } } else { - MemOpChains.push_b...

...f, NULL, > 0)); > + if (!isTailCall) > + MemOpChains.push_back(DAG.getStore(Chain, Arg, PtrOff, > NULL, 0)); > + // Calculate and remember argument location. > + else > + CalculateTailCallArgDest(DAG, MF, isPPC64, Arg, SPDiff, > ArgOffset, > + TailCallArguments); > + > inMem = true; > } > if (inMem || isMachoABI) { > @@ -1994,7 +2339,13 @@ SDOperand > PPCTargetLowering::LowerCALL(SDOperand Op, SelectionDAG &DAG, > } >...

Hello Dale, this is an updated version of the tail call optimization patch for powerpc. could you have a look at it? i added code to support ppc64 (untested, will try to get access to ppc64 on a friend's machine). incorporated evan's formatting suggestions. ;) will run another round of testing (llvm-test) on my powerpc g4/800 when i get the okay to commit. testing on this machine takes

...ion: the syscall * disabled irqs, here we enable it straight after entry: */ - sti + ENABLE_INTERRUPTS(CLBR_NONE) movl %ebp,%ebp /* zero extension */ pushq $__USER32_DS CFI_ADJUST_CFA_OFFSET 8 @@ -123,7 +130,7 @@ sysenter_do_call: call *ia32_sys_call_table(,%rax,8) movq %rax,RAX-ARGOFFSET(%rsp) GET_THREAD_INFO(%r10) - cli + DISABLE_INTERRUPTS(CLBR_NONE) TRACE_IRQS_OFF testl $_TIF_ALLWORK_MASK,threadinfo_flags(%r10) jnz int_ret_from_sys_call @@ -141,7 +148,7 @@ sysenter_do_call: CFI_REGISTER rip,rdx TRACE_IRQS_ON swapgs - sti /* sti only takes effect after the next in...

...ion: the syscall * disabled irqs, here we enable it straight after entry: */ - sti + ENABLE_INTERRUPTS(CLBR_NONE) movl %ebp,%ebp /* zero extension */ pushq $__USER32_DS CFI_ADJUST_CFA_OFFSET 8 @@ -123,7 +130,7 @@ sysenter_do_call: call *ia32_sys_call_table(,%rax,8) movq %rax,RAX-ARGOFFSET(%rsp) GET_THREAD_INFO(%r10) - cli + DISABLE_INTERRUPTS(CLBR_NONE) TRACE_IRQS_OFF testl $_TIF_ALLWORK_MASK,threadinfo_flags(%r10) jnz int_ret_from_sys_call @@ -141,7 +148,7 @@ sysenter_do_call: CFI_REGISTER rip,rdx TRACE_IRQS_ON swapgs - sti /* sti only takes effect after the next in...

...gt;> + if (!isTailCall) >> + MemOpChains.push_back(DAG.getStore(Chain, Arg, PtrOff, >> NULL, 0)); >> + // Calculate and remember argument location. >> + else >> + CalculateTailCallArgDest(DAG, MF, isPPC64, Arg, SPDiff, >> ArgOffset, >> + TailCallArguments); >> + >> inMem = true; >> } >> if (inMem || isMachoABI) { >> @@ -1994,7 +2339,13 @@ SDOperand >> PPCTargetLowering::LowerCALL(SDOperand Op, SelectionDAG &DAG, >>...

...measures, there is no remedy against it. I plan to fire each of these two rounds with one week delay and monitor the LLVM mailing lists while they are soaking. After that I'll commit the actual operand rotation. Last but not least, there will be some cleanup commits: - removing CallInst::ArgOffset, - fixing the 80-column violations I have introduced, - doxygenizing the new interfaces, - re-enabling the low-level interface again (possibly after 2.8 has brached?). Well, that's it. I hope that this order of commits will keep the pain at a bearable level for everyone. I would be...

...two rounds with one week delay and >> monitor >> the LLVM mailing lists while they are soaking. >> >> After that I'll commit the actual operand rotation. >> >> Last but not least, there will be some cleanup commits: >> >> - removing CallInst::ArgOffset, >> - fixing the 80-column violations I have introduced, >> - doxygenizing the new interfaces, >> - re-enabling the low-level interface again (possibly >> after 2.8 has brached?). >> >> Well, that's it. I hope that this order of commits will keep &g...

...> > I plan to fire each of these two rounds with one week delay and monitor > the LLVM mailing lists while they are soaking. > > After that I'll commit the actual operand rotation. > > Last but not least, there will be some cleanup commits: > > - removing CallInst::ArgOffset, > - fixing the 80-column violations I have introduced, > - doxygenizing the new interfaces, > - re-enabling the low-level interface again (possibly > after 2.8 has brached?). > > Well, that's it. I hope that this order of commits will keep > the pain at a bearabl...

...t; > I plan to fire each of these two rounds with one week delay and monitor > the LLVM mailing lists while they are soaking. > > After that I'll commit the actual operand rotation. > > Last but not least, there will be some cleanup commits: > > - removing CallInst::ArgOffset, > - fixing the 80-column violations I have introduced, > - doxygenizing the new interfaces, > - re-enabling the low-level interface again (possibly > after 2.8 has brached?). > > Well, that's it. I hope that this order of commits will keep > the pain at a bearable l...

...and >>> monitor >>> the LLVM mailing lists while they are soaking. >>> >>> After that I'll commit the actual operand rotation. >>> >>> Last but not least, there will be some cleanup commits: >>> >>> - removing CallInst::ArgOffset, >>> - fixing the 80-column violations I have introduced, >>> - doxygenizing the new interfaces, >>> - re-enabling the low-level interface again (possibly >>> after 2.8 has brached?). >>> >>> Well, that's it. I hope that this order...

...from_fork) + /* * System call entry. Upto 6 arguments in registers are supported. * @@ -223,7 +231,7 @@ ENTRY(system_call) * No need to follow this irqs off/on section - it's straight * and short: */ - sti + ENABLE_INTERRUPTS(CLBR_NONE) SAVE_ARGS 8,1 movq %rax,ORIG_RAX-ARGOFFSET(%rsp) movq %rcx,RIP-ARGOFFSET(%rsp) @@ -245,7 +253,7 @@ ret_from_sys_call: /* edi: flagmask */ sysret_check: GET_THREAD_INFO(%rcx) - cli + DISABLE_INTERRUPTS(CLBR_NONE) TRACE_IRQS_OFF movl threadinfo_flags(%rcx),%edx andl %edi,%edx @@ -261,7 +269,7 @@ sysret_check: /*CFI_REGIST...

...from_fork) + /* * System call entry. Upto 6 arguments in registers are supported. * @@ -223,7 +231,7 @@ ENTRY(system_call) * No need to follow this irqs off/on section - it's straight * and short: */ - sti + ENABLE_INTERRUPTS(CLBR_NONE) SAVE_ARGS 8,1 movq %rax,ORIG_RAX-ARGOFFSET(%rsp) movq %rcx,RIP-ARGOFFSET(%rsp) @@ -245,7 +253,7 @@ ret_from_sys_call: /* edi: flagmask */ sysret_check: GET_THREAD_INFO(%rcx) - cli + DISABLE_INTERRUPTS(CLBR_NONE) TRACE_IRQS_OFF movl threadinfo_flags(%rcx),%edx andl %edi,%edx @@ -261,7 +269,7 @@ sysret_check: /*CFI_REGIST...

...e two rounds with one week delay and >> monitor >> the LLVM mailing lists while they are soaking. >> >> After that I'll commit the actual operand rotation. >> >> Last but not least, there will be some cleanup commits: >> >> - removing CallInst::ArgOffset, >> - fixing the 80-column violations I have introduced, >> - doxygenizing the new interfaces, >> - re-enabling the low-level interface again (possibly >> after 2.8 has brached?). >> >> Well, that's it. I hope that this order of commits will keep >&g...

Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel