Date: Sat, 13 Oct 2001 23:14:13 -0700 From: Peter Wemm <peter@wemm.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: ia64@FreeBSD.ORG Subject: Re: vfprintf.c Message-ID: <20011014061413.4A1F73810@overcee.netplex.com.au> In-Reply-To: <20011013215052.A1551@dhcp01.pn.xcllnt.net>
index | next in thread | previous in thread | raw e-mail
Marcel Moolenaar wrote: > Guys, > > Do we already have a "formal" solution for libc/stdio/vfprintf.c? > I experimented with changing argtable to not store the addresses > of the varargs (which fails on ia64), but to hold the values > themselves and that works good. This is probably a pessimisation > on i386; more so than on Alpha. An alternative is to not use the > argtable at all. > > Is anybody taking a look at this? Doug already posted a patch which fixes it.. It should be committed. ==== Date: Wed, 5 Sep 2001 11:31:15 +0100 (BST) Subject: Making printf work on ia64 From: Doug Rabson <dfr@nlsystems.com> Message-id: <Pine.BSF.4.33.0109051127170.43574-100000@herring.nlsystems.com> Since the ia64 architecture has significantly different means for passing arguments than most others, it has an implementation of stdarg.h which doesn't work with our printf. In particular, you cannot take a pointer to the values returned by va_arg(). To get things to work, I had to change printf to copy the arguments instead of pointing to them. I have extensively tested this on ia64 and i386 and can't think of any problems with it. Still, it would be nice to have a few other eyes look over it. The QUAD_MAX part is down to a limitation with my ia64 build environment and should be harmless. .... ==== Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the messagehelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011014061413.4A1F73810>