search for: callee

....as | 165 ++++++++++++++++++----------------- 14 files changed, 351 insertions(+), 340 deletions(-) New commits: commit 15402b24b998b110dad41d2b1559267d474ba892 Author: Pekka Lampila <pekka.lampila at iki.fi> Date: Thu Nov 15 20:48:40 2007 +0200 Improve arguments caller/callee test somewhat diff --git a/test/trace/arguments-5.swf b/test/trace/arguments-5.swf index aece37e..50d9be0 100644 Binary files a/test/trace/arguments-5.swf and b/test/trace/arguments-5.swf differ diff --git a/test/trace/arguments-5.swf.trace b/test/trace/arguments-5.swf.trace index 02fbeb4..7e8718f...

...a while, I'm still a little confused with the meaning of the 'byval' attribute. From the langref: "This indicates that the pointer parameter should really be passed by value to the function. The attribute implies that a hidden copy of the pointee is made between the caller and the callee, so the callee is unable to modify the value in the callee. This attribute is only valid on llvm pointer arguments. It is generally used to pass structs and arrays by value, but is also valid on scalars (even though this is silly)." I'm particularly confused by the "between the calle...

Hi, byval means that the parameter setup code for performing a call copies the struct onto the stack, in an appropriate position relative to the other call parameters. > I'm particularly confused by the "between the caller and the callee" part. The > way I see this, the responsibility for the copying should be with either the > caller or the callee, It is with the caller. It would be nice to do an explicit memcpy in the caller, but the problem is that the value has to end up in a very precise place on the stack and the...

Hi Tim, Thought about it last night and was coming to the same conclusion. 1. it cant be done at the end during lowering (target backend). 2. it should be part of llvm as the byVal needs to be handled. As a twist, I have been told that llvm-gcc can lower byVal into memcpy in the callee. I may take a look at this. I wonder if it ever emits 'byVal'... I still feel I don't understand enough about where byVal is used or what it means. Is it *only* used as an attribute of an argument pointer to argument data that is pending a copy? Once the memcpy is made, I assume the by...

I was trying to do a SIP call between two Asterisk servers (1.4.21.2) 1) On the caller server, I coded the following in extensions.conf Dial(SIP/1166:password at asterisk-callee); 2) On the callee server, I coded the following in sip.conf [1166] type=friend ; Friends place calls and receive calls context=incoming ; Context for incoming calls from this user host=dynamic ; This peer register with us dtmfmode=rfc2833...

Hi Robert, suppose you have a "byval" argument with type T*, and the caller passes a T* called %X for it, while in the callee the argument is called %Y. The IR level semantics are: (1) a copy should be made of *%X. Whether the callee or the caller makes the copy depends on the platform ABI. (2) in the callee, %Y refers to the address of this copy. There are many ways (1) can be codegened, it all depends on what t...

Hi Duncan, Karel, On 14 October 2011 08:22, Duncan Sands <baldrick at free.fr> wrote: > Hi Karel, > >>>> > const unsigned* >>>> > ARMBaseRegisterInfo::getCalleeSavedRegs(const MachineFunction *MF) >>>> const { >>>> > + bool ghcCall = false; >>>> > + >>>> > + if (MF) { >>>> > + const Function *F = MF->getFunction(); >>>> > + ghcCall = (F ? F->getCallingConv() == Cal...

...id/log.h> #ifdef __cplusplus extern "C" { #endif void caller() { __android_log_print(ANDROID_LOG_DEBUG, "TEST", "%s:%d:%s", __FILE__, __LINE__, __FUNCTION__); } #ifdef __cplusplus } #endif ----------------------------------------------------------------- callee.cpp ----------------------------------------------------------------- #include <android/log.h> #ifdef __cplusplus extern "C" { #endif void callee() { __android_log_print(ANDROID_LOG_DEBUG, "TEST", "%s:%d:%s", __FILE__, __LINE__, __FUNCTION__); } #ifdef...

TLDR - I have a runtime which expects to be able to inspect certain arguments to a function even if that argument isn't used within the callee itself. DeadArgumentElimination doesn't respect this today. I want to add an argument that records an argument to a call as live even if the value is known to be not used in the callee. My use case ----------------- What my runtime is doing is trying to resolve a symbolic reference to a f...

...005,1,Dial(SIP/2000&SIP/2001&SIP/2002, 30) ' All softphones (2000, 2001 and 2002) will ring. These are proprietary softphones and all of then will reply with SIP 183 message. SIP 183 will contain SDP with media information. The question is: Will the caller receive SIP 183 from each callee? That is, will it receive 3 SIP 183 messages? It is important to the caller receives a SIP 183 message from each callee, because this caller needs to send early media (video) to every callee. Or, will Asterisk send just one message SIP 183 to the caller, with some kind of generic SDP message? Any...

...all. Function* launch = Function::Create( TypeBuilder<int(const char*, int, ...), false>::get(context), GlobalValue::ExternalLinkage, "kernelgen_launch_", m2); { CallInst* call = dyn_cast<CallInst>(cast<Value>(I)); if (!call) continue; Function* callee = call->getCalledFunction(); if (!callee && !callee->isDeclaration()) continue; if (callee->getName() != func2.getName()) continue; SmallVector<Value*, 16> callargs(call->op_begin(), call->op_end()); callargs.insert(callargs.begin(), ConstantI...

...------------------------------------------------------------ @@ -33,7 +33,8 @@ int main(int argc, char *argv[]) inst_iterator I = inst_begin((Function *)F); Instruction *inst = &*I; - CallInst::Create(callee, "", inst); + CallInst* ci = CallInst::Create(callee, "", inst); + ci->setDebugLoc(inst->getDebugLoc()); } if (F->getName() == "callee") --------------...

I am using EQTDDataStructures (from the poolalloc project) to resolve indirect function calls to over-approximated sets of possible callees. Unfortunately I find that it yields incorrect results even on a very simple test input. My LLVM and poolalloc sources are Subversion trunk checkouts, no more than a day older than the current trunk head. My test input is the following C source, compiled to bitcode using Clang: void foo();...

Duncan Sands wrote: > Hi, byval means that the parameter setup code for performing a call > copies the struct onto the stack, in an appropriate position relative > to the other call parameters. > > >> I'm particularly confused by the "between the caller and the callee" part. The >> way I see this, the responsibility for the copying should be with either the >> caller or the callee, >> > > It is with the caller. It would be nice to do an explicit memcpy in the caller, > but the problem is that the value has to end up in a ver...

...> > void caller() > { > __android_log_print(ANDROID_LOG_DEBUG, "TEST", "%s:%d:%s", > __FILE__, __LINE__, __FUNCTION__); > } > > #ifdef __cplusplus > } > #endif > ----------------------------------------------------------------- > > callee.cpp > ----------------------------------------------------------------- > #include <android/log.h> > > #ifdef __cplusplus > extern "C" { > #endif > > void callee() > { > __android_log_print(ANDROID_LOG_DEBUG, "TEST", "%s:%d:%s&quo...

Hi Karel, >>> > const unsigned* >>> > ARMBaseRegisterInfo::getCalleeSavedRegs(const MachineFunction *MF) >>> const { >>> > + bool ghcCall = false; >>> > + >>> > + if (MF) { >>> > + const Function *F = MF->getFunction(); >>> > + ghcCall = (F ? F->getCallingConv() == CallingConv::GHC : false);...

Hi Duncan, On 10/14/11 03:56 PM, Duncan Sands wrote: > Hi Karel, > >> > const unsigned* >> > ARMBaseRegisterInfo::getCalleeSavedRegs(const MachineFunction *MF) >> const { >> > + bool ghcCall = false; >> > + >> > + if (MF) { >> > + const Function *F = MF->getFunction(); >> > + ghcCall = (F ? F->getCallingConv() == CallingConv::GHC : false); >> > + } >&g...

Hi David, > The code above is needed as the GHC calling convention redefines what > registers are considered callee save. No one else rummages in to the > original function as all the other calling conventions use the same > set of callee and caller save registers, so GHC is the only one that > needs to differentiate. shouldn't the caller also know what registers are callee saved so that it can avo...

...gt; I just discussed this with vivek on IRC (and I think we agreed on this): > > Let me first state the motivation clearly to ease later discussions: > As far as the motivation for this change goes: Changing the calling > convention allows us to choose whether a register is saved by the callee or > the caller. Usually it is best to have a mix of both as too many caller > saved registers leads to unnecessary save/restores when the called function > turns out to only touch a fraction of the registers (as is typically for > smaller leaf-functions of the call graph). While too ma...

...dy, Do I understand correctly that Asterisk does not support sending INFO request? Here is the goal I want to accomplish and I'd be happy to hear how can it be done with asterisk. Asterisk needs to dial out and after successful call establishment it needs to send in-dialog INFO request to the callee and wait after that for another INFO message coming from callee. So call flow looks like the following: Asterisk -->INVITE--->Callee Asterisk<--200/OK<---Callee Asterisk-->ACK--->Callee after asterisk sends ACK it waits for several seconds and sends INFO message Asterisk-->...