On Feb 15, 2008, at 1:29 AM, Mike Frysinger wrote: > On Friday 15 February 2008, Haavard Skinnemoen wrote: >> Mike Frysinger <[EMAIL PROTECTED]> wrote: >>>> if someone can tell me what the number of args are for each arch we >>>> can see about providing this everywhere. >>> >>> are you sure you actually need to worry about such things ? i'm >>> pretty >>> sure any relevant architecture says that the first X arguments go >>> via >>> registers and the rest go on the stack. let the compiler worry >>> about the >>> exact value for X. >> >> I guess the real question is whether it's acceptable to pass >> arguments >> on the stack to such subprograms. If the answer is yes, why not >> simply >> use varargs? > > if the goal is to keep things in registers, "call" and its > description are way > too vague. the description makes me think this is meant to be a > "go" for > functions.
As per Wolfgang's desires the help is terse, the commit message was suppose to convey more details. But I can see where the confusion comes from. I'm open to better wording and will try to think of some myself. >> If the answer is no: avr32 can pass up to 5 arguments through >> registers. > > x86 does 0 while Blackfin does 3. 3 arch's down, 6 to go. - k ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
