lkml.org 
[lkml]   [2004]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Add FUTEX_CMP_REQUEUE futex op
Andrew Morton wrote:

> and we're expecting the a's and b's to line up across all architectures and
> compiler options. I thought that on some architectures that only works out
> if the function has a vararg declaration.

I never heard that.


> Does it do the right thing on stack-grows-up machines?

Would be only HP/PA and I don't see this to be a problem.


> If the compiler passes the first few args via registers and the rest on the
> stack, are we sure that it won't at some level of complexity decide to pass
> _all_ the args on the stack? It's free to do so, I think.

This is not how the calling conventions are designed. If registers are
used they happens unconditional of the remainder of the parameter list.
The stack is used as an overflow.


> I have a vague memory of getting bitten by this trick once...

I don't and, as Ingo mentioned, we already did it before.

--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:03    [W:0.609 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site