On Thu, 20 Oct 2022, Richard Biener via Gcc wrote:
> > 1. How should (...) be represented differently from unprototyped functions
> > so that stdarg_p and prototype_p handle it properly? Should I add a new
> > language-independent type flag (there are plenty spare) to use for this?
>
> I'd say u
On Thu, Oct 20, 2022 at 1:54 AM Joseph Myers wrote:
>
> C2x allows variable-argument functions declared with (...) as parameters -
> no named arguments - as in C++. It *also* allows such functions to access
> their parameters, unlike C++, by relaxing the requirements on va_start so
> it no longer
C2x allows variable-argument functions declared with (...) as parameters -
no named arguments - as in C++. It *also* allows such functions to access
their parameters, unlike C++, by relaxing the requirements on va_start so
it no longer needs to be passed the name of the last named parameter.
M
On Fri, Apr 25, 2014 at 11:27 AM, Umesh Kalappa
wrote:
>
> In our private port ,we define function_arg hook to pass the first
> three args in the reg and rest will go to stack.
>
> But for variadic functions the arguments need to pass through the stack.
>
> How we ca
Hi All,
In our private port ,we define function_arg hook to pass the first
three args in the reg and rest will go to stack.
But for variadic functions the arguments need to pass through the stack.
How we can achieve this ?? Any inputs will be appreciate.
Thank you
~Umesh
function pointer to a different type and then calling it is
undefined behaviour in C/C++. The standard does not guarantee that
this program will work.
> i) Is my compiler broken? If so, is there somewhere in GCC that
> specifically handles register/stack parameter passing for variadic
>
: Variadic functions
Date: Tue, 08 Jun 2010 09:22:28 +0200
Hi,
I am working on the OPENRISC32 (or32) architecture port of uClibc and
have run into a bit of conundrum that I was hoping someone could help me
understand a bit better. Please bear with me...
--
The preconditions:
i) The
