search for: __builtin_apply

...] 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 [m...

I would also like so tee support for __builtin_apply*. We use it in macros and such. If others are interested, please speak up. -Jan On 02/10/2013 20:51, Patrik Hägglund H wrote: > Indeed. However, I wouldn't have called variable number of arguments a "sophisticated feature". :-) > > /Patrik Hägglund > > -----Original...

The __builtin_va_arg_pack() and __builtin_va_arg_pack_len() builtins are useful in this context and, unlike __builtin_apply(), are possible to implement correctly in the general case. I believe that some GNU system headers use them when they are available, so they are probably worth supporting. I'd love to see __builtin_apply() implemented and working properly too, but on most architectures / ABIs it's possibl...

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

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

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 [m...