From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ac02560f0af03a21 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-12-31 12:47:04 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!in.100proofnews.com!in.100proofnews.com!cycny01.gnilink.net!cyclone1.gnilink.net!spamkiller2.gnilink.net!nwrdny02.gnilink.net.POSTED!0f19ed38!not-for-mail From: "Frank J. Lhota" Newsgroups: comp.lang.ada References: <3FEC43B2.5080606@noplace.com> <1072450300.440355@master.nyc.kbcfp.com> <3FEC4E89.2070804@noplace.com> <1072458199.346049@master.nyc.kbcfp.com> <3fec7c21$0$4764$61fed72c@news.rcn.com> <4iBIb.8173$qS3.498@nwrdny03.gnilink.net> <1072883131.278899@master.nyc.kbcfp.com> <1072891494.595791@master.nyc.kbcfp.com> <1072899508.453543@master.nyc.kbcfp.com> Subject: Re: GNAT parameter passing, C-style? X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: Date: Wed, 31 Dec 2003 20:47:02 GMT NNTP-Posting-Host: 151.203.242.46 X-Complaints-To: abuse@verizon.net X-Trace: nwrdny02.gnilink.net 1072903622 151.203.242.46 (Wed, 31 Dec 2003 15:47:02 EST) NNTP-Posting-Date: Wed, 31 Dec 2003 15:47:02 EST Xref: archiver1.google.com comp.lang.ada:3999 Date: 2003-12-31T20:47:02+00:00 List-Id: "Hyman Rosen" wrote in message news:1072899508.453543@master.nyc.kbcfp.com... > This is vanilla C for that platform. Varargs functions are called the > same way. The function itself will then muck about with the registers as > needed to make things work. Now I get it! The problem is that I have spent most of my career with the Intel architecture, where the paucity of registers preclude any extensive use of registers for parameter passing. Of course, passing parameters by registers avoids all of these issues, since nothing is pushed onto or popped off the stack. Thanks for the clarification.