search for: __builtin_apply_args

Interesting. Just having __builtin_apply_args() (and a correspoding __builtin_apply_args_size()), would make it possible to do a memcpy store of arguments to a (varargs) function, which sometimes is useful for our users (for debug/trace purposes). /Patrik Hägglund From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] O...

...s that data type). However, these built-in functions may interact badly with some sophisticated features or other extensions of the language. It is, therefore, not recommended to use them outside very simple functions acting as mere forwarders for their arguments. --- Built-in Function: void **__builtin_apply_args*() This built-in function returns a pointer to data describing how to perform a call with the same arguments as are passed to the current function. The function saves the arg pointer register, structure value address, and all registers that might be used to pass arguments to a...

...] On Behalf Of Krzysztof Parzyszek Sent: den 2 oktober 2013 19:12 To: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] builtin_apply? I think varargs functions would be an example of where this builtin would not work. -K On 10/2/2013 2:32 AM, Patrik Hägglund H wrote: > Interesting. Just having __builtin_apply_args() (and a correspoding > __builtin_apply_args_size()), would make it possible to do a memcpy > store of arguments to a (varargs) function, which sometimes is useful > for our users (for debug/trace purposes). > > /Patrik Hägglund > > *From:*llvmdev-bounces at cs.uiuc.edu [mailto...

I think varargs functions would be an example of where this builtin would not work. -K On 10/2/2013 2:32 AM, Patrik Hägglund H wrote: > Interesting. Just having __builtin_apply_args() (and a correspoding > __builtin_apply_args_size()), would make it possible to do a memcpy > store of arguments to a (varargs) function, which sometimes is useful > for our users (for debug/trace purposes). > > /Patrik Hägglund > > *From:*llvmdev-bounces at cs.uiuc.edu [mailto...

...> However, these built-in functions may interact badly with some > sophisticated features or other extensions of the language. It is, > therefore, not recommended to use them outside very simple functions acting > as mere forwarders for their arguments. > — Built-in Function: void * *__builtin_apply_args* () > > This built-in function returns a pointer to data describing how to perform > a call with the same arguments as are passed to the current function. > > The function saves the arg pointer register, structure value address, and > all registers that might be used to pass argum...

...tober 2013 19:12 > To: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] builtin_apply? > > I think varargs functions would be an example of where this builtin > would not work. > > -K > > > On 10/2/2013 2:32 AM, Patrik Hägglund H wrote: >> Interesting. Just having __builtin_apply_args() (and a correspoding >> __builtin_apply_args_size()), would make it possible to do a memcpy >> store of arguments to a (varargs) function, which sometimes is useful >> for our users (for debug/trace purposes). >> >> /Patrik Hägglund >> >> *From:*llvmdev-bo...

....edu >> Subject: Re: [LLVMdev] builtin_apply? >> >> I think varargs functions would be an example of where this builtin >> would not work. >> >> -K >> >> >> On 10/2/2013 2:32 AM, Patrik Hägglund H wrote: >>> Interesting. Just having __builtin_apply_args() (and a correspoding >>> __builtin_apply_args_size()), would make it possible to do a memcpy >>> store of arguments to a (varargs) function, which sometimes is useful >>> for our users (for debug/trace purposes). >>> >>> /Patrik Hägglund >>>...