search for: __builtin_apply_args_size

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] On Behalf Of Eric Christopher Sent: den 2 oktober...

...ktober 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:llvmdev-bounces at cs.uiuc.edu] > *On Behalf Of *...

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:llvmdev-bounces at cs.uiuc.edu] > *On Behalf Of *...

...; 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:llvmdev-bounces at cs.uiuc.e...

__builtin_apply is an abomination. Even in GCC it is held to have been a bad idea. --eric On Oct 1, 2013 10:03 PM, "reed kotler" <rkotler at mips.com> wrote: > why does clang not support builtin_apply? > > 6.5 Constructing Function Calls > > Using the built-in functions described below, you can record the arguments > a function received, and call another

...> >> 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:ll...

why does clang not support builtin_apply? 6.5 Constructing Function Calls Using the built-in functions described below, you can record the arguments a function received, and call another function with the same arguments, without knowing the number or types of the arguments. You can also record the return value of that function call, and later return that value, without knowing what